Skip to main content
Glama

Market Intelligence API (core)

Explain move

market.explain_move
Read-onlyIdempotent

Why is a symbol moving? ($0.10) The 15-minute move and its likely drivers from every source (on-chain flow, unusual activity, smart money, perp crowding, 48h news, SEC filings, insiders) with direction and weight, plus a one-sentence summary. Crypto, tokenized stocks and US stocks.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "market.explain_move"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYese.g. ETHUSD, NVDA, TSLA

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely non-annotated facts — a $0.10 cost and the shape of the response (drivers with direction and weight, plus a one-sentence summary). It says nothing about latency, failure modes for an unresolvable symbol, or any limits on the free-form source sweep.

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?

Front-loaded with the question and the price, so the agent gets purpose and cost in the first two tokens. The parenthetical source list is long but earns its space by telling the agent exactly what evidence backs the answer; only minor trimming is possible.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read-only tool with no output schema, the description covers purpose, cost, time window, asset coverage and the returned fields. Nothing an agent needs in order to call it correctly or interpret the result is missing.

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?

Schema coverage is 100% and the single symbol parameter is documented with examples (ETHUSD, NVDA, TSLA), so the baseline is 3. The description adds real meaning beyond the schema by declaring the accepted asset classes — crypto, tokenized stocks and US stocks — which constrains which ticker formats are valid.

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 in question form ("Why is a symbol moving?") and pins the scope: the 15-minute move plus its drivers across named source categories, with direction and weight. That framing cleanly separates it from sibling snapshot/summary tools that report state rather than causal explanation, and the supported asset classes are stated explicitly.

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 clear context for when to reach for it: an agent should use it to diagnose a recent price move, and the description states the 15-minute window plus the asset universe (crypto, tokenized stocks, US stocks). It stops short of naming alternatives (e.g. market.snapshot for current state) or stating when this is the wrong choice, so it is clear but not fully routed.

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