Skip to main content
Glama
IAcomunIA

CoinGecko MCP Server

by IAcomunIA

get_onchain_categories

Read-only

Query all supported cryptocurrency categories on GeckoTerminal to analyze market segments by volume, transactions, and fully diluted valuation.

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 categories on GeckoTerminal

Response Schema

{
  $ref: '#/$defs/category_get_response',
  $defs: {
    category_get_response: {
      type: 'object',
      properties: {
        data: {
          type: 'array',
          items: {
            type: 'object',
            properties: {
              id: {
                type: 'string'
              },
              attributes: {
                type: 'object',
                properties: {
                  description: {
                    type: 'string'
                  },
                  fdv_usd: {
                    type: 'string'
                  },
                  h24_tx_count: {
                    type: 'integer'
                  },
                  h24_volume_usd: {
                    type: 'string'
                  },
                  name: {
                    type: 'string'
                  },
                  reserve_in_usd: {
                    type: 'string'
                  },
                  volume_change_percentage: {
                    type: 'object',
                    properties: {
                      h1: {
                        type: 'string'
                      },
                      h12: {
                        type: 'string'
                      },
                      h24: {
                        type: 'string'
                      },
                      h6: {
                        type: 'string'
                      }
                    }
                  }
                }
              },
              type: {
                type: 'string'
              }
            }
          }
        }
      }
    }
  }
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNopage through results Default value: `1`
sortNosort the categories by field Default value: `h6_volume_percentage_desc`
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/).
Behavior4/5

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

Annotations provide readOnlyHint=true, but the description adds valuable behavioral context: it emphasizes performance optimization through jq_filter usage, mentions that the endpoint queries 'all' supported categories (implying potentially large datasets), and includes a detailed response schema showing the structure of returned data. This goes beyond what annotations provide by explaining practical considerations for efficient usage.

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. The performance guidance about jq_filter comes first (good front-loading), but the purpose statement is buried after it. The inclusion of the full response schema within the description text adds significant length that might be better handled through a separate output schema field. Every sentence earns its place, but the organization could be improved.

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 purpose (querying categories), 3 parameters with full schema coverage, read-only annotation, and no output schema, the description provides good context. It explains the tool's purpose, gives practical usage guidance for performance, and includes the response structure. The main gap is lack of comparison with sibling category tools, but otherwise it's reasonably complete for this type of query tool.

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 all parameters are well-documented in the schema itself. The description adds specific guidance about jq_filter ('always use... to reduce response size') and references the output schema for available fields, but doesn't provide additional semantic meaning beyond what's already in the parameter descriptions. This meets the baseline for high schema coverage.

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 supported categories on GeckoTerminal' which clearly indicates the verb (query) and resource (categories). It distinguishes from many sibling tools that focus on tokens, pools, or exchanges rather than categories. However, it doesn't specifically differentiate from 'get_list_coins_categories' or 'get_pools_onchain_categories' which also handle categories.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The description provides explicit guidance about 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'). This gives clear context for parameter usage. However, it doesn't specify when to use this tool versus alternative category-related tools like 'get_list_coins_categories' or 'get_pools_onchain_categories'.

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