Skip to main content
Glama
IAcomunIA

CoinGecko MCP Server

by IAcomunIA

get_onchain_networks

Read-only

Retrieve all supported blockchain networks from GeckoTerminal to identify available platforms for cryptocurrency data analysis and trading.

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 supported networks on GeckoTerminal

Response Schema

{
  $ref: '#/$defs/network_get_response',
  $defs: {
    network_get_response: {
      type: 'object',
      properties: {
        data: {
          type: 'array',
          items: {
            type: 'object',
            properties: {
              id: {
                type: 'string'
              },
              attributes: {
                type: 'object',
                properties: {
                  coingecko_asset_platform_id: {
                    type: 'string'
                  },
                  name: {
                    type: 'string'
                  }
                }
              },
              type: {
                type: 'string'
              }
            }
          }
        }
      }
    }
  }
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNopage through results Default value: 1
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 useful behavioral context about performance optimization with jq_filter and mentions pagination through the 'page' parameter (implied by the schema). However, it doesn't disclose other behavioral traits like rate limits, authentication needs, or response format details beyond the embedded schema, which would be helpful given no output schema is provided.

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 appropriately sized but not optimally structured. It starts with a performance tip about jq_filter before stating the core purpose, which could be front-loaded better. The embedded JSON schema adds length but is necessary due to the lack of an output schema. Some sentences like 'Only omit if you're sure you don't need the data' are somewhat redundant with the first sentence.

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

Completeness4/5

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

Given the tool's low complexity (2 optional parameters), 100% schema coverage, and readOnlyHint annotation, the description is mostly complete. It includes an embedded output schema to compensate for the missing output schema field, and it adds performance guidance. However, it could better address sibling differentiation and more explicit behavioral context to be fully comprehensive.

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 value by emphasizing the importance of 'jq_filter' for performance and providing a usage tip, and it references the output schema in the description for field availability. This goes beyond the schema's technical documentation, though it doesn't add deep semantic context for the 'page' 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 all the supported networks on GeckoTerminal' which is a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'get_asset_platforms' or 'get_network_networks_onchain_new_pools' that might also relate to networks, 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 Guidelines3/5

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

The description provides some usage guidance by emphasizing the importance of using the 'jq_filter' parameter for performance and advising to omit it only when unnecessary. However, it lacks explicit context about when to use this tool versus alternatives like 'get_asset_platforms' or other network-related siblings, leaving the agent to infer usage from the purpose statement alone.

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