Skip to main content
Glama

edge-signals

signals_bundle

Full DeFi signal bundle: funding extremes, funding spreads, DEX arb edges, and recent Aave liquidation opportunities.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It discloses the bundle's composition and notes 'recent' liquidation opportunities, but does not state whether the data is live, cached, or point-in-time, nor does it confirm the tool is read-only and side-effect free.

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?

The definition is a single front-loaded sentence that lists the bundle contents without filler. Every phrase earns its place by identifying a distinct signal category.

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

Completeness3/5

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

For a zero-parameter read tool with no output schema, the description sufficiently names the broad categories returned but does not explain the response structure, freshness windows, or how the bundled signals are combined. This is adequate to invoke the tool but leaves meaningful gaps in understanding 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 has zero input parameters, so there are no parameter semantics to explain. The baseline for a parameterless tool is 4, and the description introduces no misleading parameter expectations.

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 description names a specific composite resource and enumerates its four constituent signal types: funding extremes, funding spreads, DEX arb edges, and Aave liquidation opportunities. It clearly differentiates this aggregate from the individual signal tools, though it does not use a verb like 'retrieve' or 'list'.

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?

The word 'Full' hints that this is the comprehensive bundle, but the definition gives no explicit guidance on when to use it versus signals_funding_extremes, signals_funding_spreads, or wallet_full_bundle. There are no exclusions, prerequisites, or tradeoff notes.

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