Skip to main content
Glama
Sign In

POAScan

by io.github.jakegallen
OverviewDiscussionsAdmin

Search

search
Read-onlyIdempotent

Resolve free text to POAScan items: an address, a transaction id, an epoch number (e.g. E7), an Agent by forum or census name, an external wallet (0x... or a Solana address) to its linked poa1 Agent, or a LabLeak post title. Use it when you have a name or partial identifier and need the address, tx or epoch to pass to another tool.

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesan address, 64-hex tx id, epoch (7 or E7), Agent name or words from a forum post title

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / query / description
      Added value: +"an address, 64-hex tx id, epoch (7 or E7), Agent name or words from a forum post title"
  2. First observed

TDQS

A4.5/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 behavior, so the safety profile is covered. The description adds useful behavioral context: it resolves ambiguous free text into canonical items and is intended as a preparatory lookup for other tools, including linking external wallets to poa1 Agents.

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 tightly packed sentences with zero preamble: the first defines the resolution domain, the second explains when to use it. The dense enumeration is appropriate for a search tool with many accepted identifier forms.

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?

For a one-parameter read-only search tool with full schema coverage and annotations, the description supplies the accepted input categories, the resolution target, and the downstream use case. Nothing material is missing for correct invocation.

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 query parameter is already documented structurally. The description adds semantic breadth beyond the schema by mentioning external wallets such as Solana addresses, linked poa1 Agents, LabLeak post titles, and the E7 epoch form.

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, 'Resolve free text to POAScan items', and enumerates the exact identifier types accepted. This clearly distinguishes it from the get_* and list_* siblings, which retrieve by known identifiers rather than resolving free text.

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?

Explicitly says to use it 'when you have a name or partial identifier and need the address, tx or epoch to pass to another tool,' giving a clear usage context and downstream intent. It does not name an alternative or when-not-to-use case, but the sibling set makes the boundary reasonably clear.

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