Skip to main content
Glama

Local index freshness

index_status
Read-onlyIdempotent

Verify local Title 38 index freshness before searching: reports eCFR issue date, last sync time, row counts, corpus receipt hash, and staleness against CFR_MAX_AGE_DAYS.

Instructions

Report how current the local Title 38 index is: eCFR issue date, last sync time, row counts, the corpus receipt hash (a sha256 over the sorted per-provision (citation, text+heading) pairs at rebuild time, null on older indexes — a receipt over this index that detects ACCIDENTAL corruption of the local copy — not a signature, and no claim about the upstream text) and whether the index is stale relative to CFR_MAX_AGE_DAYS. Check this before relying on search results.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "index_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
staleYes
sectionsYes
syncedAtYes
issueDateYes
appendicesYes
corpusHashYes
maxAgeDaysYes
lastChangesYes
parserVersionYes
structureDriftYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.1
    • addedOutput schema / properties / corpusHash
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "issueDate",
      -  "syncedAt",
      -  "sections",
      -  "appendices",
      -  "stale",
      -  "maxAgeDays",
      -  "parserVersion",
      -  "structureDrift",
      -  "lastChanges"
      -]New value: +[
      +  "issueDate",
      +  "syncedAt",
      +  "sections",
      +  "appendices",
      +  "stale",
      +  "maxAgeDays",
      +  "parserVersion",
      +  "structureDrift",
      +  "corpusHash",
      +  "lastChanges"
      +]
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, closed-world), the description explains what the receipt hash actually is — a sha256 over sorted per-provision pairs computed at rebuild time — and, importantly, what it is NOT: not a signature, no claim about upstream text, null on older indexes. It also discloses the staleness criterion (CFR_MAX_AGE_DAYS). This is exactly the kind of semantic and trust-boundary context annotations cannot convey.

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

Conciseness3/5

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

The front-loading is good — the core purpose comes first — but the whole definition is a single sprawling sentence whose parenthetical about the receipt hash is dense enough to require re-reading. The caveats about the hash are valuable, yet the packaging hurts scannability.

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?

With an output schema present, return values need no explanation, and annotations cover the safety profile, so the description only needs to frame meaning and timing — which it does, including the staleness threshold and hash caveats. It could go slightly further by clarifying how its output relates to the sibling `health` tool, but nothing essential for calling it correctly is missing.

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?

There are zero input parameters, so the baseline is 4. The description still adds useful meaning by naming CFR_MAX_AGE_DAYS as the external configuration that determines the stale flag, which is not visible in the empty schema.

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?

The description opens with a specific verb and resource: "Report how current the local Title 38 index is," then enumerates the exact fields returned (eCFR issue date, last sync time, row counts, receipt hash, staleness). That is clearly distinguishable from retrieval tools like get_section or search_regulations, though it does not explicitly differentiate itself from the sibling `health` tool, which could plausibly overlap.

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?

It gives an explicit use condition: "Check this before relying on search results," which tells the agent exactly when this tool matters. It stops short of naming alternatives or stating when not to call it (e.g., how it differs from `health`), so it falls just short of full routing guidance.

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