Skip to main content
Glama

Perp Funding Rates: 5 venues in one call

Funding teaser (free): BTC on each venue

funding_peek
Read-onlyIdempotent

FREE. BTC funding (% per 8h) on each of the 5 venues, without other symbols, spreads or extremes. Use it to check the feed works from here before paying.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered elsewhere. The description adds genuinely non-obvious context: this is a free tier, deliberately truncated in scope, and intended as a connectivity smoke test. It says nothing about freshness or rate limiting, 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.

Conciseness5/5

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

Two sentences, with the most decision-relevant fact ('FREE') front-loaded and the limitation on scope immediately after. Every clause carries information; nothing is redundant with the title or annotations.

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, no-output-schema teaser, the description conveys both what comes back (BTC funding per 8h across 5 venues) and the intended purpose. The individual venues are not enumerated, which is the only real 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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly implies the caller supplies no filters, since symbols and venues are fixed by the tool.

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 a concrete resource (BTC funding, expressed as % per 8h), a definite scope (each of the 5 venues), and explicit exclusions (other symbols, spreads, extremes), so the agent can tell this apart from a full funding feed. It stops short of naming the paid sibling, but the free-tier framing makes the contrast implicit and readable.

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?

'Use it to check the feed works from here before paying' gives a clear selection rule, and the exclusions imply when to move to a richer tool. It does not explicitly name the alternative or state what to do when spreads/extremes are actually required, so it is one step short of full routing 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