Skip to main content
Glama
IAcomunIA

CoinGecko MCP Server

by IAcomunIA

get_simple_price

Read-only

Query cryptocurrency prices by coin IDs or symbols to retrieve current values in specified currencies, with options for market data and response filtering.

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 the prices of one or more coins by using their unique Coin API IDs

Response Schema

{
  $ref: '#/$defs/price_get_response',
  $defs: {
    price_get_response: {
      type: 'object',
      additionalProperties: true
    }
  }
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vs_currenciesYestarget currency of coins, comma-separated if querying more than 1 currency. *refers to [`/simple/supported_vs_currencies`](/reference/simple-supported-currencies).
idsNocoins' IDs, comma-separated if querying more than 1 coin. *refers to [`/coins/list`](/reference/coins-list).
include_24hr_changeNoinclude 24hr change percentage, 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
include_tokensNofor `symbols` lookups, specify `all` to include all matching tokens Default `top` returns top-ranked tokens (by market cap or volume)
namesNocoins' names, comma-separated if querying more than 1 coin.
precisionNodecimal place for currency price value
symbolsNocoins' symbols, comma-separated if querying more than 1 coin.
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, which the description does not contradict. The description adds value by emphasizing the jq_filter parameter for performance optimization and response size reduction, which is useful behavioral context beyond the annotations. However, it lacks details on rate limits, error handling, or data freshness.

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

Conciseness2/5

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

The description is poorly structured: it starts with a performance tip about jq_filter, then states the purpose, and includes a JSON schema snippet that belongs in an output schema field. This disrupts front-loading of key information and includes redundant elements, reducing clarity.

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

Completeness2/5

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

For a tool with 11 parameters, no output schema, and many siblings, the description is incomplete. It lacks information on response format, error cases, or usage examples. The embedded JSON schema is misplaced and does not compensate for the absence of a proper output schema.

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 schema fully documents all 11 parameters. The description does not add any parameter-specific semantics beyond what the schema provides. It mentions jq_filter generically but repeats schema information. Baseline score of 3 is appropriate given high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool 'allows you to query the prices of one or more coins by using their unique Coin API IDs', which provides a clear verb ('query') and resource ('prices of coins'). However, it does not differentiate this tool from its many siblings (like get_coins_markets or get_range_coins_market_chart), leaving ambiguity about when to use this specific tool versus others for price-related queries.

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 no guidance on when to use this tool versus alternatives. It mentions using the jq_filter parameter for performance but does not specify contexts, prerequisites, or exclusions. With many sibling tools available, the lack of comparative guidance is a significant gap.

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