Skip to main content
Glama

Perp Funding Rates: 5 venues in one call

How to pay (free)

payment_options
Read-onlyIdempotent

FREE. Prices, receiving address, the exact x402-over-MCP retry format, the 24h pass, and the equivalent plain HTTP endpoints (also payable by a plain USDC transfer on Base).

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

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 readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds that no payment is required and that plain HTTP endpoints / a USDC transfer on Base are alternatives, but says nothing about auth requirements or response format.

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 fragment with 'FREE.' front-loaded, so the key differentiator is the first token read. The comma-list of contents is slightly telegraphic but every item is informative and nothing is padded.

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 no-param, read-only informational tool with no output schema, enumerating the returned items (prices, address, retry format, pass, HTTP endpoints) effectively substitutes for a return-value description. Only auth/payment prerequisites for using the returned address are left implicit.

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 nothing to disambiguate and the baseline of 4 applies. The description's value lies in naming the returned content rather than parameter meaning.

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 title and the enumeration 'Prices, receiving address, the exact x402-over-MCP retry format, the 24h pass... endpoints' make clear this is a payment/pricing information tool rather than a data operation, and the leading 'FREE' distinguishes it from the paid funding tools. It is a noun-phrase content list rather than a verb-led statement of purpose, which costs it a point.

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?

Implied guidance only: because it is marked FREE and covers prices and retry format, an agent can infer it should be called before attempting a paid call and before funding_feed_pass. No explicit when-to-use, when-not, or named alternatives are given, so routing relies on inference.

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