Skip to main content
Glama

DeFi Capital Flow-Price Gap

Fingerprint and Bitcoin proof of a day (free)

get_proof
Read-onlyIdempotent

Free. The SHA-256 fingerprint file and the OpenTimestamps Bitcoin proof of a data day, its Bitcoin status and block, and how to verify it yourself (ready-made code: /examples/). Argument date: YYYY-MM-DD. From GET /verify/index.json.

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": {
      "date": "<date>"
    },
    "name": "get_proof"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesdata day, YYYY-MM-DD (UTC)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive and closed-world behavior, so the description's job is to add context — and it does: it discloses cost ('Free'), the upstream source (GET /verify/index.json), the returned artifacts, and that verification code is provided. It stops short of describing response shape or whether a day without a proof returns empty versus erroring.

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 dense sentence front-loads cost and the two main artifacts, followed by the format and source endpoint. It is slightly run-on — the 'how to verify it yourself' clause and the parenthetical path could be separated — but no sentence is filler.

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 explain what comes back, and it does name the fingerprint file, OTS proof, Bitcoin status/block, and verification path. For a one-parameter read tool this is nearly complete; only the concrete return format and failure behavior remain unstated.

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?

With one fully documented parameter at 100% schema coverage, the baseline is 3. The description repeats the YYYY-MM-DD format and the 'data day' framing already present in the schema, adding only minor reinforcement rather than new semantics such as valid date range or behavior for future days.

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 names a concrete resource: the SHA-256 fingerprint file plus the OpenTimestamps Bitcoin proof for a given data day, along with its Bitcoin status and block. It is clearly distinct from siblings like get_free_signal or get_track_record, though it never explicitly contrasts itself with list_free_days, which plausibly returns the same days without proofs.

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

Usage Guidelines3/5

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

Usage is only implied: 'Free.' signals there is no cost barrier, and the mention of '/examples/' signals this is the tool for self-verification. There is no explicit when-to-use versus when-not, and no pointer to a sibling for the case where the caller only wants a listing of available days.

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