Skip to main content
Glama
Alpha Sentinel Market Intelligence MCP

Alpha Sentinel Market Intelligence MCP

fetch_price

Read-onlyIdempotent

Fetch real-time cryptocurrency prices, 24-hour changes, and trading volume from CoinGecko for supported symbols to inform trade execution and position analysis.

Instructions

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 observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds genuinely new behavior beyond them: the external data source (CoinGecko), a per-call cost of $0.005 with a 'cheapest tier - high frequency allowed' characterization, and a sample payload. It stops short of stating rate limits or failure behavior for unsupported symbols.

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 purpose, then returns, use case, cost, and example in a scannable order; every block carries information. The markdown bolding and the 'Example Response' header are slightly ceremonial for a one-parameter tool, and the returns sentence partly duplicates the example.

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?

With no output schema, the inline example response fully specifies the return shape (price_usd, change_24h, volume_24h, timestamp). Cost, data source, and the single required parameter are all covered, so an agent has everything needed to call and interpret it.

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% and the single 'symbol' parameter is documented in the schema with examples ('btc', 'eth', 'sol'). The description only adds the phrase 'any supported cryptocurrency,' which hints the symbol must be in a supported set but does not enumerate or link it.

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 ('Fetch real-time cryptocurrency price from CoinGecko API') plus the exact scope of returned values. None of the sibling tools listed fetch prices, so an agent can route on this description alone without schema inspection.

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 selection context ('before executing trades or analyzing positions') and the cost note helps an agent weigh call frequency. There is no explicit when-not guidance or naming of an alternative tool, which keeps it from a 5.

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