Skip to main content
Glama

list_active_signals

Top-volatility crypto assets ranked by 1h/24h/7d change. Returns up to 10 assets.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
categoryNoSecurity, Crypto, Environment, Tech, Markets, Health, Governance, or Other
severityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden and largely drops it. It doesn't state sort direction (implicitly descending by volatility), the volatility window definition, whether results are live or cached, or auth requirements. Worse, it asserts a hard cap of 'up to 10 assets', which is a behavioral claim that contradicts the schema's limit of 1-100 with default 25.

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?

Two short, front-loaded sentences with no filler — structurally sound. However, the second sentence does not earn its place because it encodes a false constraint rather than useful information.

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?

There is no output schema, zero annotations, and three parameters of which two are undocumented, so the description needed to specify result shape, ordering, and severity/category meaning. It supplies none of that and adds a contradictory result-count claim. What an agent needs in order to call this correctly is largely absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%: only category is documented, while limit and severity have no schema descriptions. The description could have compensated by explaining the severity ladder or how limit interacts with ranking, but instead it states 'Returns up to 10 assets', directly contradicting the limit parameter's default of 25 and maximum of 100. That is actively misleading rather than merely unhelpful.

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

Purpose2/5

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

The description says it ranks 'top-volatility crypto assets' by 1h/24h/7d change, which is a specific verb+resource shape. But it conflicts with both the tool name ('signals') and the schema, whose category enum spans Security, Environment, Tech, Markets, Health and Governance — not just crypto. An agent cannot tell whether this returns market data or topical news signals.

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?

No when-to-use guidance, no exclusions, and no reference to any alternative among the many list_* siblings (list_categories, list_entities, get_sector). The agent is left to infer that this is the 'discovery/ranking' endpoint entirely on its own.

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