Skip to main content
Glama

azeth_history

Retrieve recent transaction history for your smart account to verify payments or audit activity.

Instructions

Get recent transaction history for your Azeth smart account.

Use this when: You need to review past transactions, verify a payment was sent, or audit account activity.

Returns: Array of transaction records with hash, from, to, value, block number, and timestamp.

Note: Complete history requires the Azeth indexer. When it is unavailable, this returns a best-effort recent-only window the RPC can serve and sets indexedHistoryUnavailable=true (it never errors) — treat a flagged result as partial, not as "no activity". The account is determined by the AZETH_PRIVATE_KEY environment variable.

Example: { "limit": 5 } or { "smartAccount": "#2", "limit": 20 }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainNoTarget chain. Defaults to AZETH_CHAIN env var or "baseSepolia". Accepts "base", "baseSepolia", "ethereumSepolia", "ethereum" (and aliases like "base-sepolia", "eth-sepolia", "sepolia", "eth", "mainnet").
limitNoMaximum number of transactions to return. Defaults to 10.
smartAccountNoSmart account address, name, or "#N" (account index). If omitted, uses your first smart account.
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses key behaviors: partial history when indexer unavailable, a flag indexedHistoryUnavailable=true, and that it never errors. It also explains account determination from environment variable. This exceeds minimum transparency.

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 concise with clear sections (use cases, returns, note, example). Every sentence serves a purpose, though some phrasing could be tighter.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no output schema, the description lists return fields and handles edge cases (indexer unavailability). It is complete for a history tool, covering output, limitations, and configuration.

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% with good descriptions, so baseline is 3. The description adds an example and clarifies account resolution for smartAccount. It adds marginal value beyond the schema, earning a 3.

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 clearly states the tool retrieves recent transaction history for an Azeth smart account, with specific use cases. It is distinct from sibling tools, though not explicitly contrasting them.

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 description explicitly lists when to use the tool (review past transactions, verify payment, audit activity) and notes limitations when the indexer is unavailable. It does not provide alternatives or when-not-to-use, but the context is sufficient.

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/azeth-protocol/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server