Skip to main content
Glama

Market Intelligence

market_intelligence
Read-onlyIdempotent

[$0.01 USD per call] Real-time crypto market price data

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "ETH"
    },
    "name": "market_intelligence"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesTicker symbol, e.g. ETH, SOL, BTC.
paymentNoOptional x402 payment proof (EIP-3009 signed authorization). Call once without it to receive the payment requirements, then retry with the proof.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / symbol / description
      Previous value: -"Path parameter 'symbol'"New value: +"Ticker symbol, e.g. ETH, SOL, BTC."
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "symbol": "ETH"
      +  }
      +]
  3. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful information not in the annotations: a per-call price of $0.01 USD. It does not disclose return shape, data sources, or freshness guarantees, and the x402 payment retry dance lives only in the schema.

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?

A single compact line with the cost signal front-loaded in brackets, so nothing is wasted. Brevity costs it here, though — the string is so short it omits scope and return information an agent would want.

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

Completeness2/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 carries the burden of explaining what comes back (fields, quote currency, exchange coverage), and it says nothing. The payment flow is documented in the schema, which helps, but combined with the missing usage context this is thin for a paid, open-world data tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with symbol and the x402 payment proof both documented in the schema itself, including the call-once-then-retry pattern. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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

Purpose3/5

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

"Real-time crypto market price data" names the resource and a freshness property but has no verb, so it reads as a data category rather than an action. It gives no signal distinguishing it from sibling tools like gas_oracle or token_security, which an agent must resolve by name inference alone.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no preconditions, and no mention of alternatives among the many market/data siblings. The agent is left to guess whether this is the right tool for spot price lookups versus gas or DeFi analytics.

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.