Skip to main content
Glama
IAcomunIA

CoinGecko MCP Server

by IAcomunIA

get_asset_platforms

Read-only

Query all blockchain asset platforms available on CoinGecko to identify supported networks and their native tokens for cryptocurrency analysis.

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 all the asset platforms on CoinGecko

Response Schema

{
  $ref: '#/$defs/asset_platform_get_response',
  $defs: {
    asset_platform_get_response: {
      type: 'array',
      items: {
        type: 'object',
        properties: {
          id: {
            type: 'string',
            description: 'asset platform ID'
          },
          chain_identifier: {
            type: 'number',
            description: 'chainlist\'s chain ID'
          },
          image: {
            type: 'object',
            description: 'image of the asset platform',
            properties: {
              large: {
                type: 'string'
              },
              small: {
                type: 'string'
              },
              thumb: {
                type: 'string'
              }
            }
          },
          name: {
            type: 'string',
            description: 'chain name'
          },
          native_coin_id: {
            type: 'string',
            description: 'chain native coin ID'
          },
          shortname: {
            type: 'string',
            description: 'chain shortname'
          }
        }
      }
    }
  }
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filterNoapply relevant filters to results
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 this is a safe read operation. The description adds behavioral context by emphasizing performance optimization with 'jq_filter' and noting it queries 'all' asset platforms, which suggests potentially large data volumes. However, it doesn't disclose rate limits, authentication needs, or pagination behavior. With annotations covering safety, the description adds some value but not rich behavioral details.

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 usage advice but includes a verbose output schema in the description text, which is redundant since there's no output schema in context signals. The first two sentences are efficient, but the schema duplication adds unnecessary length. It could be more concise by omitting the embedded schema or integrating it better.

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 has read-only annotations, 2 parameters with full schema coverage, and no output schema, the description is moderately complete. It covers purpose and parameter guidance but lacks details on response format (though implied by the embedded schema), error handling, or integration with siblings. For a query tool with good annotations, it's adequate but has gaps in contextual richness.

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 description coverage is 100%, so the schema fully documents both parameters. The description adds semantic context by strongly recommending 'jq_filter' for performance and explaining its purpose ('reduce the response size'), which goes beyond the schema's technical description. It also implies the 'filter' parameter's use case through the enum 'nft', though not explicitly. This compensates well, earning above the baseline 3.

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 states 'query all the asset platforms on CoinGecko', which is a clear verb+resource combination. It specifies the scope ('all the asset platforms') but doesn't explicitly differentiate from sibling tools like 'get_onchain_networks' or 'get_networks_onchain_dexes', which might have overlapping functionality. The purpose is clear but lacks sibling differentiation.

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 description provides guidance on when to use the 'jq_filter' parameter ('always use... to reduce response size and improve performance') and when to omit it ('Only omit if you're sure you don't need the data'), which implies usage context. However, it doesn't specify when to use this tool versus alternatives among the many sibling tools (e.g., for asset platforms vs. networks or other data types), leaving the agent to infer based on tool names.

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