Skip to main content
Glama

DeFi Capital Flow-Price Gap

Track record per signal tier (free)

get_track_record
Read-onlyIdempotent

Free. Track record per signal tier: backtest verdicts (A works / B partial / C not distinguishable from luck) per methodology version, observation counts, the thresholds, Bitcoin proofs, the live record and the price policy. A tier name describes the measured state, not how well it is proven. Same JSON as GET /performance.

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": "get_track_record"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds real value beyond that: it discloses the returned categories, warns that 'a tier name describes the measured state, not how well it is proven' (a critical interpretation caveat), and states the response matches GET /performance. It does not discuss freshness or caching, which keeps it from a 5.

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?

The most decision-relevant token, 'Free.', is front-loaded, and the long content list is a compact enumeration rather than prose padding. The clause about tier names is the one sentence an agent genuinely needs for correct interpretation of the results, so it earns its place. Slightly dense but well structured.

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 no parameters and no output schema, the description carries the burden of explaining return content, and it does so by naming each section of the payload. The interpretation caveat about tier names is exactly the kind of guidance an agent needs to avoid misreporting results. Freshness of the live record and whether pagination applies are the only notable omissions.

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?

The tool takes zero parameters and the schema is an empty object, so there is nothing for the description to disambiguate. Baseline 4 applies; the description correctly implies a single global snapshot rather than a query.

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 the resource precisely — 'track record per signal tier' — and enumerates its contents (backtest verdicts A/B/C, methodology versions, observation counts, thresholds, Bitcoin proofs, live record, price policy), so an agent knows what data comes back. It also pins the payload to 'Same JSON as GET /performance'. It stops short of explicitly contrasting itself with siblings such as get_free_signal or get_proof.

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?

'Free.' leading the description signals this is the no-cost tier, which implies an agent should prefer it over paid siblings when cost matters, but the definition never states when to use it versus get_signal or get_token_signal. Usage must be inferred from the tier label rather than read from explicit when/when-not guidance.

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