Skip to main content
Glama

Attestation status

attestation_status
Read-onlyIdempotent

Check if an attestation is current, stale, fragment-removed, or unanchored, and see who affirmed or declined a record at a specific commit or branch.

Instructions

Who affirmed or declined what about a record, as of which commit, and whether the record has changed since: Current (unchanged since the verdict), Stale (changed since), FragmentRemoved (the part it was about is gone), Unanchored (no commit to compare with). A stale affirmation is one a reviewer gave to an earlier version.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "type": "<type>",
      "id": "<id>"
    },
    "name": "attestation_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe record's id, as Type/local (LearningObjective/lateral-reading-check) or the local part alone.
refNoA commit id to read at, as an earlier answer named it: pass the commit from your first answer to every follow-up, so the conversation reads one state of the design. Pass this or branch, not both.
typeYesThe record's class, such as LearningObjective, AssessmentItem, Module or DesignNote.
branchNoThe branch to read at its latest commit. Leave out to read the default branch (main unless configured otherwise). Pass this or ref, not both.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description earns credit for defining the post-fetch classification semantics (Current, Stale, FragmentRemoved, Unanchored) and clarifying that a stale affirmation refers to an earlier version, which is genuinely non-obvious behavior. It does not say what comes back when a record has no attestations at all or how the verdicts are grouped.

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

Conciseness4/5

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

Two sentences, front-loaded with the question the tool answers, then a compact taxonomy. The parenthetical status definitions are dense but each carries real meaning. The trailing note about stale affirmations is slightly redundant with the Stale entry but is short enough not to be wasteful.

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

Completeness3/5

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

For a read-only, no-output-schema tool with four fully documented parameters, the description covers the semantics an agent needs to interpret the status values. However, with no output schema, some account of the return shape, for example a list of attestations with verdicts plus a status field, would help the agent use the result correctly. That omission leaves it adequate but not quite complete.

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

Parameters3/5

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

Schema coverage is 100%, so id, type, ref and branch are all documented in the schema, giving a baseline of 3. The description adds only the temporal framing ('as of which commit') and the staleness definition, which reinforces rather than extends the schema's account of ref and branch. No added detail on the Type/local id format is needed, since the schema already spells it out.

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 states a specific question the tool answers: who affirmed or declined what about a record, at which commit, and whether the record has changed since. That verb-plus-resource framing clearly separates it from get_record or record_history, which return content rather than verdict provenance. It falls short of a 5 only because it never names a sibling it is meant to replace.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not guidance, and no alternative is named. The only procedural instruction, passing the commit from your first answer to follow-ups, is really parameter advice already present in the schema. An agent must infer on its own whether to reach for this tool or for record_history/compare_record.

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