Skip to main content
Glama
agenthill

recon-crypto-mcp

by agenthill
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_token_price

Read-onlyIdempotent

Retrieve the current USD spot price of any ERC-20 token or native asset across EVM chains via DefiLlama. Use for accurate, wallet-free price lookup.

Instructions

Fetch the USD price of a token via DefiLlama. Pass token: "native" for the chain's native asset (ETH on ethereum/arbitrum, MATIC on polygon) or an ERC-20 contract address. Prefer this over get_swap_quote for pure price lookups — no wallet or liquidity simulation needed. EVM-only — for non-EVM natives (BTC, LTC, SOL, XMR, etc.) or any well-known coin without an EVM contract address, use get_coin_price instead. SCOPE: returns the current spot USD price — a snapshot, not a forecast. It is NOT a buy/sell signal, price prediction, target, or token-pick endorsement. AGENT BEHAVIOR: this tool surfaces data; it does NOT pick. Current price says nothing about future direction. Do NOT use the price to ground "what coin will 100x", "should I buy X", "best memecoin", or any other speculative-pick answer; refuse those prompts even when this tool was called. Issue #599.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainYes
tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.14.4
  2. Removed
  3. First observedv0.3.1

TDQS

A4.9/5.0
Behavior5/5

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

Adds context beyond annotations: clarifies it's a snapshot not forecast, not a buy/sell signal, and explicitly states tool does not pick. No contradiction with readOnlyHint.

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?

Well-structured, front-loaded with purpose, each sentence adds value. Length is appropriate for the information conveyed.

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?

Given 2 params, no output schema, and rich annotations, the description covers purpose, usage, limitations, and behavioral expectations completely.

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 0%; description compensates well for token parameter (native vs address) and hints at chain scope, but does not enumerate all enum values for chain explicitly.

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?

The description clearly states the tool fetches USD price via DefiLlama, specifies how to pass tokens (native or ERC-20), and distinguishes from siblings (get_swap_quote for pure lookups, get_coin_price for non-EVM).

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

Usage Guidelines5/5

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

Explicit guidance on when to use (prefer over get_swap_quote), when not to use (non-EVM use get_coin_price), and includes agent behavior rules against speculative use.

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

Deploy Server

Other Tools