List transactions for an account with pagination
| Name | Required | Description | Default |
|---|---|---|---|
| address | Yes | Account address | |
| pageSize | No | Number of transactions per page (1-100, default 10) | |
| pageToken | No | Pagination token for next page |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the behavioral disclosure burden. It communicates read-only intent and paginated behavior, but it omits details like ordering, response shape, empty-result behavior, and invalid-address handling.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is short, front-loaded with the verb and resource, and contains no filler. Every word earns its place, and the pagination qualifier adds practical value without bloating the text.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple and the schema thoroughly documents parameters, but with no annotations and no output schema, the description leaves operational context such as page contents, next-token behavior, and sorting to inference. It is sufficient for a basic call but not fully complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the input schema already documents all three parameters. The description adds no parameter-level meaning beyond the word 'pagination', so the baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description identifies the exact operation ('List transactions') and the resource scope ('for an account'), and the pagination qualifier distinguishes it from single-transaction retrieval and global recent-transaction lists. An agent can tell this apart from sibling tools like get_transaction and list_recent_transactions.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description conveys the core use case: listing account-scoped transactions with pagination. However, it does not explicitly state when to use this tool versus list_recent_transactions or search, nor does it mention exclusions or alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource or query type: account, block, transaction, program ABI, account history, recent blocks, recent transactions, and cross-entity search. The generic search tool overlaps somewhat with individual getters, but its role as a unified lookup query is clear.
Tool names consistently follow a verb_noun pattern using get_, list_, or search_. This creates a predictable structure where the verb indicates retrieval mode and the noun indicates the target entity.
Eight tools is well-scoped for a read-only blockchain explorer. The set covers core entities without unnecessary redundancy, and each tool earns its place.
The toolset covers the main explorer workflows: fetching accounts, blocks, transactions, ABIs, and paginated history. Minor gaps such as token-specific balance lookups or direct program-account enumeration exist, but they are not critical for general chain exploration.