Skip to main content
Glama

DeFi Capital Flow-Price Gap

Free data days (older than 7 days, CC BY 4.0)

list_free_days
Read-onlyIdempotent

Free. Every data day older than 7 days, free under CC BY 4.0 and byte-identical to the Bitcoin-timestamped originals: date, link to the full signal, fingerprint and Bitcoin status. Compact view of GET /free/index.json.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful context beyond them: the 7-day recency boundary, CC BY 4.0 licensing, and byte-identical correspondence to the Bitcoin-timestamped originals. It does not address ordering, result size, or pagination for a list endpoint.

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 with the key constraint (older than 7 days) front-loaded after the one-word 'Free.' opener. The word 'free' appears twice plus a licensing clause, which is mild redundancy, but nothing is padding.

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?

For a zero-parameter read tool with no output schema, the description carries its weight by enumerating the four returned fields and flagging that this is a compact projection of a larger JSON index. Ordering and volume of returned days are the only unstated details, a minor gap.

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?

Zero parameters with 100% schema coverage, so the baseline is 4. The description correctly indicates the filtering is fixed (older than 7 days) rather than caller-supplied, which prevents an agent from hunting for a date parameter that does not exist.

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 states the resource precisely: every data day older than 7 days, with the returned fields (date, link to full signal, fingerprint, Bitcoin status) enumerated. It also orients against the sibling surface by calling itself a 'compact view' whose entries link to the full signal, though it never names get_free_signal directly.

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: the 7-day cutoff and the 'link to the full signal' phrasing suggest this is an index you browse before fetching a specific day's signal. There is no explicit statement of when to choose this over get_free_signal or get_signal, and no exclusions or prerequisites.

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