Skip to main content
Glama

alpha-sentinel-mcp

fetch_price

Fetch real-time cryptocurrency price from CoinGecko API.

Returns current price, 24h change, and trading volume for any supported cryptocurrency.

Use Case: Get instant price data before executing trades or analyzing positions.

Cost: $0.005 USD per call (cheapest tier - high frequency allowed)

Example Response: { "symbol": "bitcoin", "price_usd": 67842.50, "change_24h": 2.34, "volume_24h": 28500000000, "timestamp": "2026-08-24T15:30:00Z" }

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

Input Schema

NameRequiredDescriptionDefault
symbolYesCryptocurrency symbol (e.g., 'btc', 'eth', 'sol')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 substantially more than most: it discloses the upstream source (CoinGecko), the cost per call ($0.005, cheapest tier), and that high-frequency use is allowed. The example response documents the exact returned fields, which is valuable given there is no output schema. Gaps remain: no auth/permission requirements, no error or unsupported-symbol behavior, and no explicit rate-limit number behind 'high frequency allowed'.

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 action, then organized under short bolded labels (Use Case, Cost, Example Response), which makes skimming easy. The example response block is justified because no output schema exists, so it earns its space rather than being filler.

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 one-parameter read tool with no output schema, the definition covers purpose, return shape, cost, and intended timing well. What is missing for full completeness is failure behavior (invalid or unsupported symbol) and any pagination/refresh or caching semantics an agent would need before relying on 'real-time' data.

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 coverage is 100%, so the schema already documents the single 'symbol' parameter, and the baseline of 3 applies. The description adds no syntax or normalization detail, and in fact introduces ambiguity: the example response shows "symbol": "bitcoin" while the schema examples use short forms ('btc', 'eth', 'sol'), leaving the agent unsure which form to pass.

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?

States a specific verb and resource ('Fetch real-time cryptocurrency price from CoinGecko API') plus the data returned, so the action is unambiguous. It does not name or distinguish itself from any sibling, but no sibling in the supplied list appears to overlap with spot price retrieval, so the risk of mis-selection is low.

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?

The 'Use Case' line gives concrete context: get instant price data before executing trades or analyzing positions. That is clear positive guidance, but there is no when-not-to-use clause, no mention of alternatives (e.g., for historical prices or volatility work, which siblings like analyze_volatility seem to cover), and no statement about what to do for unsupported symbols.

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.