Skip to main content
Glama
Sign In

POAScan

by io.github.jakegallen
OverviewDiscussionsAdmin

Recent transactions

list_transactions
Read-onlyIdempotent

The latest archived transactions across the network, newest first, optionally narrowed to one type and/or one address. Use it for 'what is happening now'. For one address's complete history with paging use get_address.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoonly this tx type, e.g. challenge, grade-sealed, attest-batch, join, transfer, swap-offer or swap-fill; the result's types lists every type seen
limitNomaximum txs to return (1 to 200, default 20)
addressNoonly txs sent or received by this poa1... address

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / address / description
      Added value: +"only txs sent or received by this poa1... address"
    • addedInput schema / properties / limit / description
      Added value: +"maximum txs to return (1 to 200, default 20)"
    • addedInput schema / properties / type / description
      Added value: +"only this tx type, e.g. challenge, grade-sealed, attest-batch, join, transfer, swap-offer or swap-fill; the result's types lists every type seen"
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description adds real behavior beyond that: results are archived, returned newest-first, and scoped to a recent window (paging is implied to live only in get_address). It does not quantify how far back the archive reaches, which keeps this below a 5.

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?

Two sentences, zero filler, with ordering and filter scope front-loaded before the sibling routing instruction in the second sentence. Every clause carries information.

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 small read-only list tool with full schema coverage and annotations, the description covers purpose, ordering, filtering and the key alternative. Without an output schema it could say slightly more about what each returned transaction contains or how far back the archive goes, but nothing essential is missing.

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% and all three parameters are documented there, including the type enum examples and the limit range. The description only restates that filtering is optional by type and/or address, adding little beyond the schema, so the baseline 3 applies.

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 (list) and resource (transactions) with scope qualifiers: 'latest archived transactions across the network, newest first, optionally narrowed to one type and/or one address.' It explicitly contrasts itself with the sibling get_address, so an agent can distinguish them without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit use case ('what is happening now') and an explicit alternative with the condition that selects it ('For one address's complete history with paging use get_address'). The routing decision is fully determined by the description text.

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

All POAScan toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources