Skip to main content
Glama

Read source text

document
Read-onlyIdempotent

Read official record text using the exact collection, id and generation returned by search. Start at offset 0 with length 1 to 16,000 characters, then use next_offset unchanged for the next chunk. Does not fetch arbitrary URLs or paths.

Input Schema

NameRequiredDescriptionDefault
idYesStable ID of a known public record.
lengthNoCharacters to return, from 1 to 16,000. Smaller chunks may be needed to fit the response byte budget.
offsetNoCharacter offset for the next bounded text chunk.
collectionYesPublic record collection returned by search.
generationNoRetained snapshot UUID; omit for the current snapshot.

Output Schema

NameRequiredDescriptionDefault
idYes
textYes
offsetYes
coverageNoPresent for exclusion text chunks, with the same source-age policy as detail.
generationYes
provenanceNoSource metadata attached to the retained record.
next_offsetNo
document_kindYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / length / description
      Previous value: -"Characters to return, up to 16,000."New value: +"Characters to return, from 1 to 16,000. Smaller chunks may be needed to fit the response byte budget."
    • addedInput schema / properties / length / maximum
      Added value: +16000
    • changedInput schema / properties / length / minimum
      Previous value: -0New value: +1
  2. Changed3 schema fields changed
    • addedOutput schema / $defs / SourceFreshness / properties / attention_required
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / $defs / SourceFreshness / properties / warn_age_seconds
      Added value: +{
      +  "description": "Early-warning boundary, separate from the stale-source boundary.",
      +  "format": "int64",
      +  "type": "integer"
      +}
    • changedOutput schema / $defs / SourceFreshness / required
      Previous value: -[
      -  "state",
      -  "evaluated_at",
      -  "max_age_seconds"
      -]New value: +[
      +  "state",
      +  "evaluated_at",
      +  "max_age_seconds",
      +  "warn_age_seconds",
      +  "attention_required"
      +]
  3. Changed4 schema fields changed
    • addedOutput schema / $defs / ExclusionCoverage
      Added value: +{
      +  "properties": {
      +    "freshness": {
      +      "$ref": "#/$defs/SourceFreshness",
      +      "description": "Fresh, stale, unknown or unavailable, with age and the 24-hour warning policy."
      +    },
      +    "observed_at": {
      +      "description": "Observation time does not replace the official source timestamp.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "scope": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "sha256": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "source_date": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "source_url": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "status": {
      +      "description": "Present as unavailable when no SAM coverage exists in this generation.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    }
      +  },
      +  "required": [
      +    "freshness"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / $defs / FreshnessState
      Added value: +{
      +  "enum": [
      +    "fresh",
      +    "stale",
      +    "unknown",
      +    "unavailable"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / $defs / SourceFreshness
      Added value: +{
      +  "properties": {
      +    "evaluated_at": {
      +      "description": "UTC time when age was evaluated; source and observation dates are unchanged.",
      +      "type": "string"
      +    },
      +    "max_age_seconds": {
      +      "description": "Explicit warning threshold for this daily snapshot. Not a scheduler promise.",
      +      "format": "int64",
      +      "type": "integer"
      +    },
      +    "source_age_seconds": {
      +      "description": "Age of the official source timestamp, never the import or enrichment timestamp.",
      +      "format": "int64",
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "state": {
      +      "$ref": "#/$defs/FreshnessState"
      +    },
      +    "warning": {
      +      "description": "User-facing warning, or null when within the warning threshold.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    }
      +  },
      +  "required": [
      +    "state",
      +    "evaluated_at",
      +    "max_age_seconds"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / coverage
      Added value: +{
      +  "anyOf": [
      +    {
      +      "$ref": "#/$defs/ExclusionCoverage"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Present for exclusion text chunks, with the same source-age policy as detail."
      +}
  4. Changed6 schema fields changed
    • addedInput schema / properties / collection / description
      Added value: +"Public record collection returned by search."
    • addedInput schema / properties / generation / description
      Added value: +"Retained snapshot UUID; omit for the current snapshot."
    • addedInput schema / properties / id / description
      Added value: +"Stable ID of a known public record."
    • addedInput schema / properties / length / description
      Added value: +"Characters to return, up to 16,000."
    • addedInput schema / properties / offset / description
      Added value: +"Character offset for the next bounded text chunk."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$defs": {
      +    "JsonObject": {
      +      "description": "Source-specific JSON map. The envelope is stable; map keys vary by official source.",
      +      "type": "object"
      +    }
      +  },
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "properties": {
      +    "document_kind": {
      +      "type": "string"
      +    },
      +    "generation": {
      +      "type": "string"
      +    },
      +    "id": {
      +      "type": "string"
      +    },
      +    "next_offset": {
      +      "format": "uint",
      +      "minimum": 0,
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "offset": {
      +      "format": "uint64",
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    "provenance": {
      +      "anyOf": [
      +        {
      +          "$ref": "#/$defs/JsonObject"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "Source metadata attached to the retained record."
      +    },
      +    "text": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "generation",
      +    "id",
      +    "text",
      +    "offset",
      +    "document_kind"
      +  ],
      +  "type": "object"
      +}
  5. Added

TDQS

A4.1/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so safety is covered. The description adds real behavioral value beyond them: the chunking/pagination protocol (offset 0, fixed length cap, carry next_offset unchanged) and the bounded-fetch guarantee.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the core action, then pagination, then the exclusion. No redundant restatement of the name or title, and every sentence carries an instruction.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return-value description is unnecessary, and the pagination mechanics are explained. Enough to call the tool correctly; the only soft spot is the ambiguous next_offset reference that an agent must map onto the response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds workflow meaning the schema lacks: the exact source of collection/id/generation values and the offset/length progression. It notably references next_offset, a response field not present as a parameter, which is useful but slightly confusing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Read official record text") and ties the operation to values returned by search, which implicitly separates it from the sibling search/detail tools. However it never names an alternative tool, so the sibling differentiation is by inference rather than explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear operational guidance: use the exact collection/id/generation from search, start at offset 0 with length 1–16,000, then reuse next_offset. It also states an exclusion ("Does not fetch arbitrary URLs or paths"). It stops short of naming alternatives such as detail for metadata.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.