Skip to main content
Glama
IAcomunIA

CoinGecko MCP Server

by IAcomunIA

get_id_simple_token_price

Read-only

Query cryptocurrency token prices using contract addresses to get current USD value, 24-hour changes, trading volume, and market capitalization data.

Instructions

When using this tool, always use the jq_filter parameter to reduce the response size and improve performance.

Only omit if you're sure you don't need the data.

This endpoint allows you to query one or more token prices using their token contract addresses

Response Schema

{
  $ref: '#/$defs/token_price_get_id_response',
  $defs: {
    token_price_get_id_response: {
      type: 'object',
      properties: {
        last_updated_at: {
          type: 'number',
          description: 'last updated timestamp'
        },
        usd: {
          type: 'number',
          description: 'price in USD'
        },
        usd_24h_change: {
          type: 'number',
          description: '24hr change in USD'
        },
        usd_24h_vol: {
          type: 'number',
          description: '24hr volume in USD'
        },
        usd_market_cap: {
          type: 'number',
          description: 'market cap in USD'
        }
      }
    }
  }
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
contract_addressesYesthe contract addresses of tokens, comma-separated if querying more than 1 token's contract address
vs_currenciesYestarget currency of coins, comma-separated if querying more than 1 currency. *refers to [`/simple/supported_vs_currencies`](/reference/simple-supported-currencies).
include_24hr_changeNoinclude 24hr change default: false
include_24hr_volNoinclude 24hr volume, default: false
include_last_updated_atNoinclude last updated price time in UNIX , default: false
include_market_capNoinclude market capitalization, default: false
precisionNodecimal place for currency price value
jq_filterNoA jq filter to apply to the response to include certain fields. Consult the output schema in the tool description to see the fields that are available. For example: to include only the `name` field in every object of a results array, you can provide ".results[].name". For more information, see the [jq documentation](https://jqlang.org/manual/).
Behavior3/5

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

Annotations indicate readOnlyHint=true, confirming this is a safe read operation. The description adds some behavioral context by emphasizing performance optimization with jq_filter and noting the tool queries prices via contract addresses. However, it lacks details on rate limits, error handling, or data freshness (e.g., how 'last_updated_at' relates to real-time accuracy), which would be valuable given the financial nature of the data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is moderately concise but poorly structured. It starts with a performance tip about jq_filter, which is useful but not front-loaded with the core purpose. The inclusion of a full JSON output schema within the description text is redundant and disrupts flow, as this could be better handled in a separate output schema field. Sentences are clear but could be more efficiently organized.

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?

Given the tool's complexity (9 parameters, financial data) and annotations (readOnlyHint only), the description is somewhat incomplete. It lacks output schema integration (though one is embedded, it's not structured), and doesn't cover error cases or data limitations. However, the high schema coverage and clear purpose provide a baseline, but more context on data sources or accuracy would enhance completeness.

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 high at 89%, so the schema already documents most parameters well. The description adds minimal value beyond the schema, only implicitly referencing 'contract_addresses' and 'vs_currencies' in the purpose statement. It doesn't explain parameter interactions or provide examples beyond the jq_filter note, which is covered in the schema's description for that parameter.

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 clearly states the tool's purpose: 'query one or more token prices using their token contract addresses.' This specifies the verb ('query'), resource ('token prices'), and key input ('token contract addresses'). However, it doesn't explicitly differentiate from sibling tools like 'get_simple_price' or 'get_coins_markets,' which might also retrieve price data, leaving some ambiguity about when to choose this specific tool.

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?

The description provides minimal usage guidance. It advises to 'always use the `jq_filter` parameter to reduce response size and improve performance,' but offers no context on when to use this tool versus alternatives like 'get_simple_price' or other sibling tools. There's no mention of prerequisites, such as needing valid contract addresses or supported vs_currencies, which are required parameters.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/IAcomunIA/MCP_firts'

If you have feedback or need assistance with the MCP directory API, please join our Discord server