Skip to main content
Glama

edge-signals

token_price

Spot token price, market cap, and volume by CoinGecko id or Base ERC20 address.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
idNoCoinGecko id, e.g. ethereum
addressNoBase ERC20 contract (alternative to id)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations at all, the description carries the full behavioral burden and mostly doesn't. 'Spot' hints at a real-time quote, but there is nothing on price freshness/caching, rate limits, chain restriction to Base for address lookups, error behavior when both or neither key are given, or whether results are read-only and side-effect free.

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?

A single sentence with no filler, front-loading the output fields and then the accepted identifiers. Every clause earns its place.

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

Completeness3/5

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

For a two-parameter read lookup this is minimally adequate, and the missing output schema means return shape needn't be explained. However, with zero annotations the definition should still say something about the neither-param case and about quote freshness for a tool whose core promise is a 'spot' price.

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%, so the baseline is 3: the schema already explains 'CoinGecko id, e.g. ethereum' and 'Base ERC20 contract (alternative to id)'. The description restates these without adding selection logic, precedence rules, or format details.

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?

The description names specific returned fields (price, market cap, volume) and both lookup keys (CoinGecko id or Base ERC20 address), so the resource is unambiguous. It does not differentiate itself from analysis-oriented siblings like token_risk_before_buy or token_verdict_before_buy, which is the only thing keeping it from a 5.

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

Usage Guidelines3/5

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

The phrase 'by CoinGecko id or Base ERC20 address' implies the two lookup modes, but there is no explicit guidance on choosing between them, no statement of what happens when neither is supplied (both params are optional), and no routing to sibling tools. Usage is inferable but not stated.

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