Skip to main content
Glama

APEX Runner Crypto Signals

portfolio_heat

$0.007 — Call this before increasing exposure so you don't add risk into a market-wide selloff — returns a market heat % from the 24h average price drop and Fear & Greed, a SAFE / CAUTION / HIGH / CRITICAL status, and an action recommendation.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/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 disclose the cost ($0.007), the computational basis, and the exact return structure including a status classification and action recommendation. It implies a read-only check ('before increasing exposure') without explicitly stating no side effects, and says nothing about permissions or rate limits.

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

Conciseness5/5

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

One dense sentence that front-loads cost, then the decision context, then the outputs. Every clause earns its place: price, trigger, inputs, statuses, and recommendation are all decision-relevant.

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, the description must explain return values and it does — heat percentage, four-tier status, and an action recommendation. What is missing is the scale or thresholds behind the heat % and what the recommendation field looks like, which matters for interpreting CRITICAL vs HIGH.

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 the baseline is 4. The description is consistent with that, describing a global market measure with no filtering or scoping inputs, and it adds no false implication that arguments are needed.

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

Purpose5/5

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

States a specific verb and resource ('returns a market heat %') plus the exact computation inputs (24h average price drop and Fear & Greed) and the output categories (SAFE / CAUTION / HIGH / CRITICAL). This distinguishes it from sibling sentiment tools like fear_greed because it explicitly says it blends price action with sentiment rather than reporting sentiment alone.

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?

Gives a clear trigger condition: 'Call this before increasing exposure so you don't add risk into a market-wide selloff.' That is genuine when-to-use guidance tied to a decision point. No when-not-to-use case or named alternative is offered, which keeps it below 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