Skip to main content
Glama

APEX Runner Crypto Signals

grid_health_score

$0.007 — Grid efficiency health score for APEX's own live grid bots across Kraken, Coinbase and Hyperliquid — cycle velocity, per-pair P&L per dollar deployed, and the best-performing pair. ⚠️ APEX's grid engines are currently PAUSED, so this reports the HISTORICAL RECORD of real past grid activity, not live telemetry. Every response carries engine_status, engine_paused_since and the per-venue last-cycle timestamps.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does substantial work: it discloses the cost ($0.007), the engine PAUSED state, engine_paused_since, and that responses include engine_status and per-venue last-cycle timestamps. The key trap — mistaking historical data for live telemetry — is called out explicitly. Minor gaps remain on latency, rate limits, or auth mechanics.

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?

Well front-loaded: price, then purpose and metrics, then the critical state caveat. Three dense sentences with no filler, though the heavy em-dash chaining makes it slightly harder to scan than a plainer structure would.

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

Completeness4/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 compensates by naming the metrics returned and the always-present status fields. An agent knows what it will get and that the numbers are historical. A brief note on staleness bounds of the per-venue timestamps would close the remaining gap.

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; the baseline for a 0-param tool is 4. Nothing in the description confuses the absence of inputs.

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?

States a specific resource and computation — grid efficiency health score for APEX's own live grid bots on Kraken, Coinbase and Hyperliquid — and enumerates the three metrics produced (cycle velocity, per-pair P&L per dollar deployed, best-performing pair). It does not explicitly name the sibling grid_health or contrast itself with it, so differentiation must be inferred from the 'APEX's own grid bots' scoping.

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

Usage Guidelines3/5

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

No explicit when-to-use or when-not guidance and no named alternative. However, the paused-engine caveat implicitly tells the agent this tool is good for historical/performance review rather than live monitoring, which is meaningful usage context even if not framed as guidance.

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