Skip to main content
Glama

Snapshot context spans

snapshot

pin invariants verbatim pre-compaction (classify + hash-pin spans)

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": {
      "event_id": "<event_id>",
      "spans": "<spans>"
    },
    "name": "snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
spansYes
event_idYes
pinned_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; they say nothing about persistence, overwriting, or hashing. The description adds meaningful behavior beyond them – that content is preserved verbatim, classified, and hash-pinned prior to compaction – but leaves unclear whether prior snapshots are replaced and what state is written.

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?

A single compact line with the key timing constraint (pre-compaction) front-loaded, so nothing is wasted. The parenthetical is terse to the point of being cryptic rather than verbose.

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

Completeness2/5

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

This is a state-mutating operation embedded in a compaction workflow, with no output schema, no parameter descriptions, and two required parameters. The description does not cover return values, effects on existing snapshots, or how it relates to the sibling pin tool, so an agent lacks enough to invoke it confidently.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry the parameter burden and does not: spans, event_id, and pinned_ids are never explained. At best "spans" can be inferred from the word "spans" in the parenthetical; pinned_ids and event_id remain entirely undefined.

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

Purpose3/5

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

"Pin invariants verbatim pre-compaction" states a verb and a resource (invariant spans) plus a timing condition, but the parenthetical "classify + hash-pin spans" is jargon that only partially clarifies the operation. Nothing distinguishes it from the sibling tool "pin", which appears to share the same verb.

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?

The description implies the tool is used before compaction but never states when to choose this over the siblings "pin", "reinject", or "audit". With a near-identically named sibling, the absence of routing guidance is a real gap.

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.

Resources