Skip to main content
Glama

APEX Runner Crypto Signals

market_tick

$0.014 — Minimal live price tick at $0.02 ($0.014 charged) — BTC, ETH, SOL plus one-word regime, Fear & Greed, and momentum label. Absolute minimum JSON payload for maximum polling speed. Designed for agents calling 1,000+ times per day. Cache: 30 seconds.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does real work: it discloses the 30-second cache, the intentionally tiny payload, the target call volume, and the price. It omits auth requirements and any explicit rate-limit or failure behavior beyond the cache hint, leaving a modest gap.

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?

Price and content are front-loaded, and every sentence carries information about cost, payload, or intended call volume. The opening '$0.014 — ... at $0.02 ($0.014 charged)' repeats the same figure twice, which is mild waste in an otherwise tight definition.

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 enumerating the returned fields and the cache window, which is what an agent needs to decide whether this payload suffices. Given the tool's deliberate minimalism, little else is required.

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 nothing for the description to disambiguate and the baseline is 4. The description correctly avoids inventing inputs and instead spends its words on what the caller receives.

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 states a specific resource set (BTC, ETH, SOL prices plus one-word regime, Fear & Greed, and momentum label) and frames it as a minimal live price tick, so an agent knows exactly what comes back. It does not name a sibling like btc_price_tick or get_free_market_snapshot to contrast against, so differentiation is inferable rather than stated.

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

Usage Guidelines4/5

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

Usage is clearly framed: 'Designed for agents calling 1,000+ times per day' and 'for maximum polling speed' tell the agent this is the high-frequency polling choice, implicitly steering richer needs elsewhere. No alternative tool is named and no explicit when-not condition is given, which keeps it short of a 5.

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