Skip to main content
Glama

BTCDecoded Intelligence

get_snapshot

Read-onlyIdempotent

Replay a stored dated report, or return a corpus manifest. Free. A 64-character id replays one tool result and does not re-search. An id such as S1109 returns that collection manifest (date, script commit, filters, counts). It does not re-judge.

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": {
      "id": "<id>"
    },
    "name": "get_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYessnapshot_id from a prior tool result, or a corpus id such as S1109.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"snapshot_id from a prior tool result."New value: +"snapshot_id from a prior tool result, or a corpus id such as S1109."
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the bar is lower, but the description still adds real value: the call is free, replay does not re-run a search, and it does not re-judge. It also enumerates what the manifest contains (date, script commit, filters, counts), which the 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.

Conciseness4/5

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

Four short sentences, front-loaded with the core purpose and cost before the id-shape branching. The telegraphic style ('Free.', 'It does not re-judge.') is efficient, though a couple of fragments are slightly terse for a reader unfamiliar with the domain.

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?

There is no output schema, so the description must describe returns, and it does so for the manifest case (date, script commit, filters, counts) and implies a stored tool result for the replay case. The only minor gap is that the exact return shape of a 64-character replay is left implicit.

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% and the schema already describes the id as a snapshot_id or corpus id, so the baseline is 3. The description goes further by specifying the 64-character format for a replay id and tying each id shape to a distinct return behavior, which is meaning beyond the 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+resource pair ('Replay a stored dated report, or return a corpus manifest') and then splits the two behaviors by id shape, so an agent knows exactly what comes back. It does not explicitly name which sibling to use for fresh lookups, though 'does not re-search' gestures at the boundary with search.

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 concrete selection criteria: a 64-character id replays one stored result, while an id like S1109 returns a collection manifest. It also states the negative cases ('does not re-search', 'does not re-judge'), which is clear context for choosing this tool over an analysis or search call, though no alternative is named explicitly.

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