Skip to main content
Glama
IAcomunIA

CoinGecko MCP Server

by IAcomunIA

get_networks_onchain_dexes

Read-only

Retrieve supported decentralized exchanges (DEXs) for a specific blockchain network from GeckoTerminal to analyze trading platforms and liquidity sources.

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 decentralized exchanges (DEXs) based on the provided network on GeckoTerminal

Response Schema

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
networkYes
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 indicate readOnlyHint=true, so the agent knows this is a safe read operation. The description adds value by emphasizing performance optimization with 'jq_filter' and noting the data source ('GeckoTerminal'), but it doesn't disclose other behavioral traits like rate limits, pagination details (beyond the 'page' parameter in schema), or error handling. No contradiction with annotations exists.

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 somewhat front-loaded with a performance tip, but it includes an embedded JSON output schema that duplicates structured data, adding unnecessary length. Sentences like 'Only omit if you're sure you don't need the data' are vague and don't earn their place, reducing 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 annotations cover read-only safety and schema has moderate coverage, the description is minimally adequate. However, it lacks output schema integration (has_output_schema=false but includes JSON in description), doesn't explain return values or pagination fully, and misses sibling differentiation. For a query tool with 3 parameters, it's functional but has clear gaps.

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 67%, with 'jq_filter' well-documented in the schema but 'network' and 'page' lacking descriptions. The description doesn't add meaning beyond the schema: it mentions 'jq_filter' for performance but repeats schema info, and it doesn't clarify 'network' (e.g., expected format) or 'page' usage. Baseline is 3 due to moderate 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 clearly states the tool's purpose: 'query all the supported decentralized exchanges (DEXs) based on the provided network on GeckoTerminal.' It specifies the verb ('query'), resource ('supported decentralized exchanges'), and scope ('based on the provided network'), though it doesn't explicitly differentiate from sibling tools like 'get_onchain_networks' or 'get_exchanges_tickers' that might handle related data.

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 'jq_filter' for performance but doesn't explain when this tool is appropriate compared to sibling tools such as 'get_exchanges_tickers' or 'get_onchain_networks', leaving the agent without context for selection.

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