vordium-mcp

Funding

get_funding

Read-onlyIdempotent

The funding rate, interval and next settlement for one market, and optionally its past settlements. Ask: "What has ETH funding been over the last day?"

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

Input Schema

Name	Required	Description
`symbol`	No	market symbol as get_markets lists it, e.g. BTC, ETH or ETHUSDT
`history`	No	also return this many past settlements, 1-400
`pair_id`	No	or the market's pair id, e.g. 1

Output Schema

Name	Required	Description
`market`	No
`history`	No
`network`	Yes	testnet or mainnet
`pair_id`	No
`summary`	Yes	one plain sentence
`next_funding`	No
`interval_secs`	No
`rate_per_interval_pct`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

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 open-world, so the safety profile is covered. The description adds that past settlements are optional and bounded by the history parameter, but says nothing about error behavior for an unknown symbol or missing pair id. With rich annotations the added context is modest, so a 3 is appropriate.

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?

Two sentences, front-loaded with the returned data, followed by a short illustrative question that helps routing. No filler, though the example adds little beyond the already-clear statement of scope.

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 read-only single-market lookup with an output schema and full parameter coverage, the description supplies enough to call it correctly. Return format is delegated appropriately to the output schema.

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 description coverage is 100%, so symbol, history (1-400) and pair_id are already documented in the schema. The description only reinforces that exactly one market is queried and that history is optional, adding no format or precedence detail beyond the baseline.

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 verb-like resource set -- funding rate, interval, next settlement -- scoped to 'one market' with optional history. An agent can tell this returns funding data rather than trades or fills, though no sibling is named explicitly for contrast.

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?

The 'Ask: "What has ETH funding been over the last day?"' example gives a concrete usage scenario and implicitly shows when history is relevant. No explicit when-not or alternative tool is offered, but the intended context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All vordium-mcp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.