Skip to main content
Glama
IAcomunIA

CoinGecko MCP Server

by IAcomunIA

get_addresses_networks_simple_onchain_token_price

Read-only

Retrieve cryptocurrency token prices using contract addresses and network information, with optional market data like 24-hour changes, volume, and market capitalization.

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 get token price based on the provided token contract address on a network

Response Schema

{
  $ref: '#/$defs/token_price_get_addresses_response',
  $defs: {
    token_price_get_addresses_response: {
      type: 'object',
      properties: {
        data: {
          type: 'object',
          properties: {
            id: {
              type: 'string'
            },
            attributes: {
              type: 'object',
              properties: {
                h24_price_change_percentage: {
                  type: 'object',
                  additionalProperties: true
                },
                h24_volume_usd: {
                  type: 'object',
                  additionalProperties: true
                },
                last_trade_timestamp: {
                  type: 'object',
                  additionalProperties: true
                },
                market_cap_usd: {
                  type: 'object',
                  additionalProperties: true
                },
                token_prices: {
                  type: 'object',
                  additionalProperties: true
                },
                total_reserve_in_usd: {
                  type: 'object',
                  additionalProperties: true
                }
              }
            },
            type: {
              type: 'string'
            }
          }
        }
      }
    }
  }
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
networkYes
addressesYes
include_24hr_price_changeNoinclude 24hr price change, default: false
include_24hr_volNoinclude 24hr volume, default: false
include_inactive_sourceNoinclude token price data from inactive pools using the most recent swap, default: false
include_market_capNoinclude market capitalization, default: false
include_total_reserve_in_usdNoinclude total reserve in USD, default: false
mcap_fdv_fallbackNoreturn FDV if market cap is not available, default: false
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 provide readOnlyHint=true, indicating a safe read operation. The description adds value by emphasizing performance optimization with 'jq_filter' and noting that omitting it should be done only if data isn't needed. However, it lacks details on rate limits, authentication needs, error conditions, or response format beyond the embedded schema. With annotations covering safety, the description adds some context but not rich behavioral traits.

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 front-loaded with performance advice and purpose, but it includes an embedded JSON output schema that duplicates information better placed in a structured output_schema field. This adds bulk without earning its place in the description text. The core description is concise, but the schema inclusion reduces structural efficiency.

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 9 parameters, 78% schema coverage, readOnlyHint annotation, and no output schema, the description is moderately complete. It states the purpose and performance tip but lacks output explanation (though schema is embedded), usage context, and error handling. For a tool with many parameters and no output schema, it should provide more guidance on response interpretation and tool selection.

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 78%, which is high, so the baseline is 3. The description doesn't add meaning beyond what the schema provides for parameters like 'network' or 'addresses.' It mentions 'jq_filter' for response reduction but repeats schema info. No additional syntax, format, or usage examples are given for parameters, so it doesn't compensate for the 22% coverage gap.

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: 'get token price based on the provided token contract address on a network.' This is a specific verb+resource combination (get + token price) that distinguishes it from many siblings focused on pools, exchanges, or NFTs. However, it doesn't explicitly differentiate from similar tools like 'get_id_simple_token_price' or 'get_simple_price,' which might also retrieve token prices.

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 doesn't specify scenarios where this tool is preferred over siblings like 'get_id_simple_token_price' or 'get_simple_price.' There's no mention of prerequisites, exclusions, or comparative contexts.

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