Skip to main content
Glama

Bitquery Token Transfers

bitquery_token_transfers
Read-onlyIdempotent

Recent transfers of a token, ERC-20 transfer events for a token contract on an EVM chain (Bitquery). Returns transfer time, sender, receiver, amount, and tx hash. Example: bitquery_token_transfers({ token: "0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48", 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": "0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48",
      "_apiKey": "your-bitquery-token",
      "network": "eth"
    },
    "name": "bitquery_token_transfers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax transfers to return (default 20, max 50).
tokenYesERC-20 token contract address. Required.
_apiKeyYesBitquery OAuth access token (Bearer). Generate at bitquery.io (free Developer tier).
networkNoEVM network enum (default "eth"). See bitquery_dex_trades for options.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 return fields (transfer time, sender, receiver, amount, tx hash), which is useful because there is no output schema. However, it leaves 'Recent' undefined and does not mention ordering, freshness window, or rate limits, so behavioral context remains partial.

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 the purpose in the first clause, followed by return fields and an example. It is compact and readable, though the example duplicates the input schema's examples, making it slightly less efficient than it could be.

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?

For a simple read-only list tool with four fully documented parameters, the description covers purpose, return fields, and an example. It is still incomplete because 'Recent' is not defined and result ordering or freshness behavior is unstated, which an agent might need to interpret results correctly.

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 the schema already documents all four parameters, including limit defaults and the meaning of _apiKey. The description's example repeats values already present in the schema's examples array, adding little new semantic guidance beyond what is structured.

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 a specific verb and resource: 'Recent transfers of a token, ERC-20 transfer events for a token contract on an EVM chain'. This is clear enough for an agent to understand it lists transfer events, distinct from related tools like token holders or DEX trades by resource name alone. However, it does not explicitly differentiate itself from sibling tools in the text.

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 gives no guidance on when to use this tool versus alternatives such as bitquery_token_holders or bitquery_dex_trades. It also omits any prerequisites or exclusions, leaving the agent to infer usage from the purpose statement alone.

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.