Skip to main content
Glama

APEX Runner Crypto Signals

grid_health

$0.007 — Simplified grid health snapshot for Kraken APEX grid bots. Returns active pairs, fill rate, and health classification.

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

Input Schema

NameRequiredDescriptionDefault
coinNoCryptocurrency symbolBTC
levelsNoNumber of grid levels
spacing_pctNoCurrent grid spacing as percentage (e.g. 0.8 = 0.8%)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does disclose the return contents and the cost ($0.007), which is genuine behavioral value. However it never states that this is a read-only computation, whether it requires an authenticated account or live bot, or how the passed grid parameters influence the result.

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

Conciseness4/5

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

A single tight sentence with no filler, and the output list is packed in efficiently. Leading with the price rather than the purpose is slightly awkward for front-loading, which keeps it short of a 5.

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?

With no output schema and no annotations, the description does reasonable work by enumerating the three return fields. It remains incomplete about the read-only nature, the meaning of the inputs relative to the returned snapshot, and how this differs from grid_health_score, all of which an agent needs to call it 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%, so all three parameters (coin, levels, spacing_pct) are already documented with types, defaults, and an enum — baseline 3 applies. The description adds no meaning beyond the schema, notably omitting that levels and spacing_pct are meant to describe the caller's existing bot configuration rather than to configure a new one.

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 concrete resource (grid health snapshot) and scope (Kraken APEX grid bots) and enumerates the outputs: active pairs, fill rate, health classification. It falls short of a 5 because the closest sibling, grid_health_score, is never named or contrasted, leaving only the weak hint in "Simplified" to distinguish the two.

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 or when-not-to-use guidance, and no alternative is named despite grid_health_score sitting right beside it in the catalog. The only guidance is implicit scope ("for Kraken APEX grid bots"), which is not enough to route an agent between the two grid tools.

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