Skip to main content
Glama

Covalent Transactions

covalent_transactions
Read-onlyIdempotent

Recent transactions for wallet X on chain Y, latest on-chain transactions for an address with USD-valued amounts and gas. Works across 100+ chains via Covalent/GoldRush. Example: covalent_transactions({ address: "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045", chain: "eth-mainnet", _apiKey: "your-key" })

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": {
      "chain": "eth-mainnet",
      "_apiKey": "your-covalent-api-key",
      "address": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"
    },
    "name": "covalent_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoChain name (Covalent format), e.g. "eth-mainnet", "matic-mainnet", "base-mainnet", "bsc-mainnet", "arbitrum-mainnet". A numeric chain id also works. Default "eth-mainnet".
_apiKeyYesCovalent / GoldRush API key (free tier at goldrush.dev)
addressYesWallet address (0x...), ENS name, or other supported domain

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds useful context (USD valuation, gas included, multi-chain coverage via Covalent/GoldRush) but says nothing about result limits, pagination, or rate limits on a read-only listing tool.

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 with the core purpose in the first clause, followed by supporting detail and a concrete example. The example largely duplicates the schema's examples array, which is mild redundancy but not harmful.

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?

With no output schema, the description carries the burden of describing returns; it does mention USD-valued amounts and gas, which helps. However, it omits pagination, result caps, and time-window semantics for 'recent', leaving meaningful gaps for a data-retrieval tool.

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 chain, address, and _apiKey are already documented in the schema, including defaults and accepted formats. The description's example call restates those parameters without adding new semantics, so the 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 resource (recent on-chain transactions) with scope (wallet X on chain Y) and adds that amounts are USD-valued with gas. It is clearly distinguishable from covalent_token_balances by resource type, though it never names a sibling explicitly.

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 only implied by the phrase 'recent transactions for wallet X on chain Y'; there is no explicit when-to-use, when-not-to-use, or pointer to an alternative tool for historical or filtered queries. The '100+ chains' note gives context but not selection guidance.

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.