Skip to main content
Glama

DeFi Capital Flow-Price Gap

Full signal of a free day (older than 7 days)

get_free_signal
Read-onlyIdempotent

Free. The full daily signal (all tokens: protocol capital inflow vs price gap, tier and reason, holder value fields, risk flag) of a data day older than 7 days, CC BY 4.0, with its proof fields. Argument date: YYYY-MM-DD (see list_free_days). Same JSON as GET /free/{date}/signal.json. Informational, not investment advice.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds valuable context: it is free, CC BY 4.0 licensed, includes proof fields, mirrors a specific JSON endpoint, and carries an informational disclaimer. It does not mention rate limits or auth, but none are implied.

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 description is a single dense paragraph that front-loads 'Free.' and the signal contents. It is appropriately sized for the complexity, though the parenthetical listing could be slightly more 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?

Given one parameter, no output schema, and read-only annotations, the description is complete enough: it describes return contents, licensing, date format, and a reference to list_free_days. The external JSON endpoint reference is not further explained, but field listing compensates.

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?

Schema coverage is 100%, so the schema fully documents the single date parameter with pattern and UTC note. The description only adds a pointer to list_free_days for valid dates, which is minor added 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?

States a specific resource and scope: 'full daily signal ... of a data day older than 7 days', and details the contents (all tokens, protocol capital inflow vs price gap, tier and reason, holder value fields, risk flag). It clearly implies a getter for free older days, though it does not explicitly name a sibling alternative for recent days.

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?

Provides clear context: only for data days older than 7 days, and points to list_free_days for obtaining valid date arguments. Does not explicitly state what to use for days within 7 days, so the exclusion is implied rather than fully guided.

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