Skip to main content
Glama

fundinglens__rates

Normalized 8h and annualized funding for many symbols across 7 venues. Price: $0.01 per call in USDC on Base (eip155:8453), paid with x402 in params._meta["x402/payment"]. HTTP: GET https://api.firstmention.uk/s/fundinglens/rates

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

Input Schema

NameRequiredDescriptionDefault
symbolsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / venues
      Removed value: -{
      -  "type": "string"
      -}
  2. Changed1 schema field changed
    • addedInput schema / properties / venues
      Added value: +{
      +  "type": "string"
      +}
  3. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description does useful work by disclosing cost ($0.01 per call), the payment rail (USDC on Base, x402 via params._meta), and the HTTP endpoint. It does not disclose rate limits, what happens on missing/unpaid payment, or the shape of the returned data, so the behavioral picture 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.

Conciseness4/5

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

Three short segments that front-load the capability before billing and transport details; no filler. Slight density in the payment/x402 clause, but every sentence carries information an agent needs before calling.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 should compensate further, yet it never says what a result contains (per-venue, per-symbol fields), and the only parameter's format is unexplained. Cost and endpoint are covered, but a caller still cannot construct a correct request confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the single parameter 'symbols' is a bare string with no documented format (comma-separated? repeated? venue-prefixed?) and no stated default despite being optional. The description says 'many symbols' but adds no syntax or meaning beyond that, leaving the one parameter effectively undocumented.

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?

'Normalized 8h and annualized funding for many symbols across 7 venues' names a specific resource (funding rates), a normalization (8h/annualized), and a batch scope, which distinguishes it from single-result siblings like fundinglens__best. It stops short of an explicit 'use this instead of X' contrast, but the purpose itself is unambiguous.

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 phrase 'for many symbols' implies batch usage and hints at when the tool is the right pick, but there is no explicit when-not guidance, no mention of how many symbols is sensible, and no named alternative. Usage is inferable rather than stated.

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