GunSpec

All 39 single-call tools

Read a GunSpec documentation guide

  • gunspec_read_docs
  • Explorer
  • Read-only

Returns one GunSpec documentation guide as Markdown. Pass the anchor of a section from gunspec_search_docs to read just that section, which is what an answer usually needs; omit it for the whole page, which can run to tens of kilobytes. Quote what this returns rather than paraphrasing from memory, and cite the url. Call gunspec_search_docs first unless the guide id is already known.

Example usage

  1. 1

    A person asks

    • Read the GunSpec caching guide and tell me how long I may keep a firearm record.
  2. 2

    The assistant calls the tool

    tools/call
    json
    {  "name": "gunspec_read_docs",  "arguments": {    "guide": "caching",    "anchor": "caching-policy"  }}
  3. 3

    The server answers

    Result
    json
    {  "id": "caching",  "title": "Caching and refreshing",  "url": "https://docs.gunspec.io/en/caching#caching-policy",  "sections": [    {      "anchor": "caching-policy",      "title": "How long you may keep it",      "trail": "How long you may keep it",      "markdown": "Every lifetime below is the value the API sends in Cache-Control on that path. There is no separate policy to remember: this table is generated from the one the server stamps responses from.\n\n| Resource | Your cache | Shared caches | Condit…"    }  ]}

    Captured from the live API on Oct 22, 2026. Lists and long text are shortened for display.

Related references

Arguments

  • stringrequired

    The guide id, e.g. "caching", "pagination", "errors" or "rate-limits".

  • string

    A section anchor from gunspec_search_docs. Omitted, the whole page is returned.

    Sent as
    ?anchor=

Each argument is sent to GET /v1/docs/guides/{id} as the parameter shown, so the same request can be made to the API directly, with your key, if you want to shape what comes back.

json