Skip to main content
Glama

edge-signals

signals_funding_spreads

Hyperliquid vs Bitget funding spread scan.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden and provides almost none: it does not say whether the call is read-only, whether it hits live exchange APIs (and thus could be slow or rate-limited), or whether results are cached. For an external-venue data pull, the absence of any latency, freshness, or failure-mode context is a real gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

It is a single fragment with no waste, and the two venues are front-loaded, but it is under-specified rather than concise — six words is not enough to carry the tool's contract. A short clause describing what the spread output is would cost little and add much.

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

Completeness2/5

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

With no annotations and no output schema, the description is the only source of truth, and it never says what comes back (a ranked spread list? a per-asset diff? symbols covered?). For a zero-parameter scan whose return shape is entirely undocumented elsewhere, that leaves the agent unable to predict or use the result.

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 does not need to compensate for any schema gap here.

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

Purpose3/5

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

Names two concrete venues (Hyperliquid, Bitget) and the resource ('funding spread'), which is more specific than a bare title, but 'scan' is the only verb and the fragment never states what the scan produces or compares (absolute spread, APY, ranking). It also gives no signal distinguishing it from the sibling signals_funding_extremes, so an agent must guess which funding tool to pick.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of an alternative tool for related funding questions. The agent is left to infer from the name alone whether this is the right entry point versus signals_funding_extremes or signals_bundle.

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