Skip to main content
Glama
IAcomunIA

CoinGecko MCP Server

by IAcomunIA

get_tokens_networks_onchain_trades

Read-only

Query recent on-chain trades for a specific token across all pools on a network to analyze trading activity and volume within the past 24 hours.

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 the last 300 trades in the past 24 hours, across all pools, based on the provided token contract address on a network

Response Schema

{
  $ref: '#/$defs/trade_get_response',
  $defs: {
    trade_get_response: {
      type: 'object',
      properties: {
        data: {
          type: 'array',
          items: {
            type: 'object',
            properties: {
              id: {
                type: 'string'
              },
              attributes: {
                type: 'object',
                properties: {
                  block_number: {
                    type: 'integer'
                  },
                  block_timestamp: {
                    type: 'string'
                  },
                  from_token_address: {
                    type: 'string'
                  },
                  from_token_amount: {
                    type: 'string'
                  },
                  kind: {
                    type: 'string'
                  },
                  pool_address: {
                    type: 'string'
                  },
                  pool_dex: {
                    type: 'string'
                  },
                  price_from_in_currency_token: {
                    type: 'string'
                  },
                  price_from_in_usd: {
                    type: 'string'
                  },
                  price_to_in_currency_token: {
                    type: 'string'
                  },
                  price_to_in_usd: {
                    type: 'string'
                  },
                  to_token_address: {
                    type: 'string'
                  },
                  to_token_amount: {
                    type: 'string'
                  },
                  tx_from_address: {
                    type: 'string'
                  },
                  tx_hash: {
                    type: 'string'
                  },
                  volume_in_usd: {
                    type: 'string'
                  }
                }
              },
              type: {
                type: 'string'
              }
            }
          }
        }
      }
    }
  }
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
networkYes
token_addressYes
trade_volume_in_usd_greater_thanNofilter trades by trade volume in USD greater than this value Default value: 0
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 discloses the 300-trade limit, 24-hour time window, and cross-pool scope. It also includes performance guidance about using jq_filter to reduce response size. While it doesn't mention rate limits or authentication needs, it goes beyond annotations by specifying operational constraints and optimization advice.

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 important usage advice and purpose, but includes an extensive output schema that duplicates information better placed in structured fields. The first two sentences are valuable, but the schema listing adds bulk without earning its place in the description text, reducing overall efficiency.

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 complexity (trade querying with multiple filters) and the presence of annotations (readOnlyHint) but no output schema, the description does well: it explains the query scope, provides performance advice, and includes the response structure. However, it could better address parameter interactions or error cases. The output schema in the description partially compensates for the lack of structured output schema.

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 50% (2 of 4 parameters have descriptions). The description doesn't explicitly explain any parameters beyond what's in the schema. However, it implies the purpose of network and token_address through the query context. With moderate schema coverage, the description doesn't compensate significantly but doesn't contradict the schema either, warranting the baseline score.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 the last 300 trades in the past 24 hours, across all pools, based on the provided token contract address on a network.' This specifies the verb ('query'), resource ('trades'), scope ('last 300 trades in the past 24 hours, across all pools'), and distinguishes it from siblings like get_pools_networks_onchain_trades (which focuses on pools) or get_tokens_networks_onchain_info (which provides general token info).

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 on when to use the tool: for querying recent trades for a specific token on a network. It distinguishes from siblings by specifying the trade-focused nature, though it doesn't explicitly name alternatives or state when not to use it. The jq_filter advice adds practical usage context, but lacks explicit exclusions or comparisons to other trade-related tools.

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