Skip to main content
Glama
@cryptoapis-io/mcp-transactions-data

@cryptoapis-io/mcp-transactions-data

Official

CryptoAPIs reference info

system_info
Read-onlyIdempotent

Retrieve CryptoAPIs reference documentation on supported blockchains, error codes, credit costs, webhook callbacks, and rate limits without consuming API credits or making API calls.

Instructions

CryptoAPIs reference documentation — no API call, no credits consumed.

Actions: • blockchains — Supported blockchains, networks, products per chain, denominations, fiat currencies • errors — Complete error code table (HTTP status, error code, message) • credits — Credit charging structure, cost multipliers per blockchain, monitoring & operations taxes (xPub, synced addresses, blockchain events), pay-as-you-go • callbacks — Webhook mechanics: URL requirements, retry strategy (5 retries, exponential backoff), HMAC security, idempotency • limits — Throughput soft/hard limits per plan, 2.1x penalty multiplier, rate limiting behavior

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "system_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesReference topic to retrieve
contextNoOptional context for the request - echoed back in response

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety bar is met; the description adds the genuinely useful cost property (zero credits, no outbound call) that annotations do not express. It also discloses the substance of each reference topic, though it does not say what the response looks like (e.g., text vs. structured data).

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

Conciseness5/5

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

Front-loaded with the single most decision-relevant fact (no call, no credits), then a tight bulleted list where each line maps one-to-one to an enum value. No filler sentences and nothing repeated from the schema verbatim.

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 two-parameter read-only lookup with no output schema, the description covers what the agent needs to choose an action and know it is free. The only gap is the shape of the returned content, which matters slightly more here because there is no output schema to fall back on.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description goes further by explaining what content each of the five action enum values actually returns (error code table, credit multipliers, retry/backoff mechanics, per-plan limits). The optional 'context' parameter is left to the schema, which is acceptable.

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?

States a specific verb and resource up front: reference documentation for CryptoAPIs, explicitly noting 'no API call, no credits consumed.' The five enumerated actions make the scope of the tool concrete and distinguish it immediately from the only sibling, broadcast_signed_transaction, which is an actual write call.

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 'no API call, no credits consumed' framing gives a clear condition for selecting this tool — consult it for static reference material rather than spending credits on live endpoints. What is missing is an explicit 'when not to use' clause or a pointer to which live endpoint to call after reading a given topic.

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