Skip to main content
Glama
IAcomunIA

CoinGecko MCP Server

by IAcomunIA

get_pools_networks_onchain_trades

Read-only

Query the last 300 trades within 24 hours for a specific pool address to analyze on-chain trading activity and transaction data.

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 based on the provided pool address

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'
                  },
                  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
pool_addressYes
tokenNoreturn trades for token use this to invert the chart Available values: 'base', 'quote' or token address Default value: 'base'
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/).
Behavior3/5

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

Annotations provide readOnlyHint=true, indicating a safe read operation. The description adds behavioral context by stating it queries 'the last 300 trades in the past 24 hours', which sets a limit and time window not covered by annotations. However, it doesn't disclose other traits like rate limits, authentication needs, or error handling, so it adds some value but not rich behavioral details beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with usage advice and purpose, using two sentences plus a note on response schema. It avoids unnecessary fluff, but the inclusion of a full JSON output schema in the description text adds bulk that could be streamlined if an output schema field were used instead, slightly 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 the tool has annotations (readOnlyHint) and a detailed input schema, the description covers the core purpose and a key parameter tip. However, with no output schema provided separately (though embedded in the description), it lacks explicit return value explanation, and for a tool with 5 parameters and moderate schema coverage, it should do more to clarify usage context and parameter interactions to be fully complete.

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 60%, with parameters like 'token' and 'trade_volume_in_usd_greater_than' having descriptions in the schema. The description mentions using 'jq_filter' to reduce response size, adding practical advice beyond the schema. However, it doesn't explain the semantics of 'network' or 'pool_address' (which are required but undocumented in the description), so it partially compensates but doesn't fully address the coverage gap.

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 the last 300 trades in the past 24 hours based on the provided pool address', which clearly specifies the action (query), resource (trades), and scope (last 300 trades in 24 hours for a pool). However, it doesn't explicitly differentiate from sibling tools like 'get_tokens_networks_onchain_trades' or 'get_pools_networks_onchain_info', which might handle similar data, so it misses full sibling distinction.

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 guidance by emphasizing to 'always use the `jq_filter` parameter to reduce response size and improve performance', which implies a best practice for usage. However, it doesn't specify when to use this tool versus alternatives (e.g., compared to 'get_tokens_networks_onchain_trades' for token-specific trades or 'get_pools_networks_onchain_info' for pool details), leaving usage context implied rather than explicit.

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