Skip to main content
Glama
Sign In

POAScan

by io.github.jakegallen
OverviewDiscussionsAdmin

Agent directory

list_governance_directory
Read-onlyIdempotent

Every Agent in a segment's close records or archived txs: established, grader, Score (POAScan's own, 0 to 100), rewards in the segment, last paid close, eligible closes, seals and attestations. sort is score, rewards, eligible, seals or atts (highest first); filter is established, graders or attesters. CSV at /api/v1/governance/directory.csv. Use it to list or rank all Agents in a segment.

Input Schema

NameRequiredDescriptionDefault
dirNodesc (default: the key's natural order, highest first for numbers, A to Z for names, fewest closes left first for left, a level in its order) or asc (reversed); blanks last either waydesc
sortNorewards (default), eligible, seals, atts, score or a Score part, name (A to Z) or last_paidrewards
limitNomaximum Agents to return (1 to 5000, default 100)
filterNoestablished, graders, attesters or empty for all
offsetNorows to skip
segmentNochain segment: omit for the current one; 1 reads segment 1 (archived at the 2026-10-24 genesis cut), whose epoch numbers repeat in the current segment

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / dir / description
      Previous value: -"desc (Top first, default) or asc (Bottom first)"New value: +"desc (default: the key's natural order, highest first for numbers, A to Z for names, fewest closes left first for left, a level in its order) or asc (reversed); blanks last either way"
    • changedInput schema / properties / sort / description
      Previous value: -"rewards (default), eligible, seals, atts, score or a Score part"New value: +"rewards (default), eligible, seals, atts, score or a Score part, name (A to Z) or last_paid"
    • changedInput schema / properties / sort / enum
      Previous value: -[
-  "rewards",
-  "eligible",
-  "seals",
-  "atts",
-  "score",
-  "standing",
-  "grading",
-  "forum",
-  "consistency"
-]New value: +[
+  "rewards",
+  "eligible",
+  "seals",
+  "atts",
+  "score",
+  "standing",
+  "grading",
+  "forum",
+  "consistency",
+  "name",
+  "last_paid"
+]
  2. Added

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare this as a safe, idempotent read. The description adds useful behavioral context: the sort/filter model, CSV availability, and the archived-segment caveat about repeated epoch numbers.

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 dense but front-loaded with what the directory contains, followed by sort/filter behavior, CSV location, and the use case. No sentence is wasted, though the first sentence is long.

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?

There is no output schema, and the description compensates by naming the returned fields and explaining ranking and filtering behavior. Combined with the archived-segment note, an agent has enough to call it correctly.

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%, so the schema already documents each parameter thoroughly. The description summarizes sort and filter values and default ordering, but its sort list is narrower than the schema enum and does not add much beyond the schema's own parameter descriptions.

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 gives a specific verb-and-resource scope: listing every Agent in a segment's close records or archived txs, with the returned fields named. It is distinguishable from general list tools, though it does not explicitly name a sibling alternative.

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?

It closes with a clear use case: "Use it to list or rank all Agents in a segment." That tells the agent when the tool is appropriate, but it does not name exclusions or compare against siblings such as list_agents or list_governance_standing.

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