APEX Runner Crypto Signals

apex_trial

$0.00 — Free market snapshot — regime, Fear & Greed, BTC price, and a 2-of-6-pillar alpha score preview (preview_only: true). No payment required. For the full 6-pillar score and its DEPLOY / WAIT / REDUCE / AVOID verdict, call apex_alpha_score. Early Adopter: 30% off every signal, automatic for every wallet until 2027-01-01.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It usefully discloses that the call is free, requires no payment, and returns preview_only data, but it does not mention rate limits, data freshness, or any operational constraints beyond pricing and preview scope.

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?

The core purpose is front-loaded and easy to scan, but '$0.00 — Free' and 'No payment required' are redundant, and the Early Adopter discount sentence is promotional rather than useful for selecting or invoking the tool.

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?

For a zero-parameter snapshot tool with no output schema, the description supplies enough context to know what data comes back and that the alpha score is only a preview. It could be more complete about freshness or response structure, but the essential selection information is present.

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 burden and the baseline score of 4 applies. The description does not need to explain input values beyond confirming that no payment or inputs are required.

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 clearly identifies a free market snapshot and enumerates its contents: regime, Fear & Greed, BTC price, and a 2-of-6-pillar alpha score preview. It also explicitly distinguishes itself from apex_alpha_score for the full score, though it does not address the similarly named get_free_market_snapshot sibling.

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?

It gives clear usage context: use this for a free preview, and call apex_alpha_score for the full six-pillar score and verdict. It does not state exclusions or prerequisites beyond the preview limitation, and it gives no guidance relative to get_free_market_snapshot.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All APEX Runner Crypto Signals tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?