Skip to main content
Glama

Bitquery Dex Trades

bitquery_dex_trades
Read-onlyIdempotent

Recent DEX trades for a token, swaps involving an ERC-20 token across DEXs on an EVM chain (Bitquery). Returns trade time, DEX/protocol, buy & sell currency + amounts, price, tx hash, and maker. Example: bitquery_dex_trades({ token: "0xdAC17F958D2ee523a2206206994597C13D831ec7", network: "eth", limit: 20, _apiKey: "your-bitquery-token" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 20,
      "token": "0xdAC17F958D2ee523a2206206994597C13D831ec7",
      "_apiKey": "your-bitquery-token",
      "network": "eth"
    },
    "name": "bitquery_dex_trades"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax trades to return (default 20, max 50).
tokenYesERC-20 token contract address (e.g. "0xdAC17F958D2ee523a2206206994597C13D831ec7"). Required.
_apiKeyYesBitquery OAuth access token (Bearer). Generate at bitquery.io (free Developer tier).
networkNoEVM network enum (default "eth"). Options: eth, bsc, matic, arbitrum, base, optimism, avalanche, fantom, cronos, gnosis, klaytn, moonbeam, opbnb.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful context by listing returned fields and showing an example call with a Bitquery OAuth token, but says nothing about rate limits, API-tier throttling, result ordering, or failure modes (e.g., invalid token address).

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?

Front-loaded purpose sentence followed by return fields, with a single compact example. Slightly redundant because the example largely restates schema defaults, but no wasted prose.

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?

For a read-only fetch with full schema coverage and no output schema, listing the returned fields and demonstrating a call is close to complete. Gaps are minor: ordering ('recent' is not precisely defined), pagination beyond the limit cap, and any error behavior for unsupported networks.

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 coverage is 100%, and the schema already documents limit (default 20, max 50), the network enum list, the token address format, and _apiKey generation. The description's example reinforces the values but adds no semantics beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource: 'Recent DEX trades for a token, swaps involving an ERC-20 token across DEXs on an EVM chain', and enumerates the return fields (time, DEX, currencies, amounts, price, tx hash, maker). The scope (EVM chain, ERC-20, DEX swaps) implicitly distinguishes it from token-holder or transfer tools, though no sibling is named outright.

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?

Usage is implied by the phrasing 'recent DEX trades for a token' and the worked example shows a concrete call, but there is no explicit when-to-use vs when-not guidance, no mention of limits/pagination constraints on data retrieval, and no named alternative for other Bitquery queries.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.