Skip to main content
Glama
Sign In
pathiel

pathiel

by Julian-dev28
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_funding_regime

Read-only

Assess market-wide funding regimes to see whether longs or shorts pay to hold across crypto, equity, and commodity assets, and identify coins with extreme funding before taking a side.

Instructions

Get the market-wide funding regime: whether longs or shorts are paying to hold (crowded) overall and per asset class (crypto, equity, commodity), with the coins whose funding is most extreme (funding as the hourly rate). asset_class narrows the coin list to one class; limit caps it (default 25, max 1000), most extreme first. Use to judge crowding before taking a side. For one coin's funding use get_market; for every coin ranked by funding use list_markets view=funding. Read-only; needs no key. Returns {regime, regimes_by_class, assets[]: {asset, asset_class, funding_rate, regime, oi, volume_24h}, assets_total}.

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

Input Schema

NameRequiredDescriptionDefault
limitNoAssets listed, most extreme funding first (default 25, max 1000).
asset_classNoOnly list assets of this class.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only declare readOnlyHint, but the description adds that no API key is needed, that funding is expressed as an hourly rate (unit semantics), that results are ordered most-extreme-first, and what the response contains. It falls short of stating rate limits or freshness of the funding snapshot, but adds substantial context beyond the annotation.

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?

Everything is packed into a front-loaded paragraph: what it returns, parameter semantics, usage routing, then the output shape. No filler sentences; every clause carries a constraint or a routing decision.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description supplies the return structure ({regime, regimes_by_class, assets[]...}), auth requirements, and scoping behavior, which is everything needed to call and interpret this zero-required-parameter tool correctly.

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% and the schema already documents limit (default 25, max 1000) and asset_class narrowing. The description restates both rather than adding syntax, units, or edge-case behavior for them, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get the market-wide funding regime') plus what that means ('whether longs or shorts are paying to hold'), and explicitly contrasts with get_market and list_markets view=funding. The agent can distinguish it from siblings without reading any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit decision rule ('Use to judge crowding before taking a side') and names two alternatives with the exact condition selecting each: get_market for a single coin, list_markets view=funding for full rankings. When-not guidance is implicit in those named alternatives.

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

Deploy Server

Other Tools