Skip to main content
Glama

edge-signals

signals_funding_extremes

Hyperliquid perpetual funding APR outliers.

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

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 none of it: no indication of data freshness, how an 'outlier' is defined (percentile, absolute threshold), how many results come back, or whether the call hits a live exchange API. The safe-read nature is only inferable from the absence of parameters, not stated.

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 non-redundant sentence with no padding, so nothing is wasted. However, the brevity comes at the cost of under-specification rather than efficiency; one clause on output shape or outlier definition would earn its place.

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 place an agent can learn what this returns, and it discloses only the data domain. 'Outliers' relative to what, over what window, and in what form remain unknown, leaving the agent unable to predict the response before calling.

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 and the schema is an empty object, so there is nothing for the description to disambiguate at the parameter level. Baseline 4 applies for a no-argument tool.

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?

The phrase 'Hyperliquid perpetual funding APR outliers' names a specific resource and a data filter (outliers), which is more concrete than a tautology. But it is a bare noun phrase with no verb, so it is unclear whether the tool lists, scans, or ranks outliers, and nothing distinguishes it from the sibling signals_funding_spreads.

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 statement of when to call this tool, when not to, or what alternative to use. An agent cannot tell from the definition whether this is a screening tool for extreme funding or the general funding view that signals_funding_spreads might cover.

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