Skip to main content
Glama
Sign In

AgentData — crypto market data with a checkable record

by io.github.speteai
OverviewDiscussionsAdmin

get_funding_accuracy

Track record of our funding predictions scored against the rates observed afterwards, over 30 days ($0.015 USDC).

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_funding_accuracy"
  }
}

Input Schema

NameRequiredDescriptionDefault
paymentNoOptional. Base64 x402 payment payload you signed yourself (ERC-3009 TransferWithAuthorization, USDC on Base). Call without it once to receive the payment requirements, sign those, then call again with this argument. This server forwards the payload and never holds a key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

B3.4/5.0
Behavior3/5

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

Without annotations, the description carries the behavioral burden. It discloses a cost ($0.015 USDC) and the scoring methodology (predictions vs observed rates over 30 days), which is useful. It does not mention response format, payment-flow behavior, or side effects beyond the fee, so disclosure is partial.

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

Conciseness5/5

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

One sentence conveys purpose, time window, and cost without filler. The key scoping phrase ('scored against the rates observed afterwards, over 30 days') is front-loaded.

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?

There is no output schema, and the description does not state what the returned accuracy data looks like (metrics, format, granularity). It also relies on the input schema to explain the payment flow, so an agent cannot fully anticipate response or behavior from the description alone.

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?

The schema already documents the payment parameter fully, including the call-without-payment flow and security property, so schema coverage is 100%. The description adds only cost context and does not elaborate on the parameter, matching the baseline of 3.

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 phrase 'Track record of our funding predictions scored against the rates observed afterwards' clearly identifies the tool as an accuracy-reporting endpoint for funding predictions over a 30-day window. It is distinguishable from siblings like get_funding_predictions and get_funding_rates, though the nominal form 'track record' lacks an explicit verb.

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?

The description implies the tool is for checking past prediction accuracy against realized rates, but it does not explicitly state when to choose it over similar siblings such as get_signal_calibration or get_signal_history_30d. No exclusions or alternative routing are provided, leaving usage to inference.

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

All AgentData — crypto market data with a checkable record toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources