Skip to main content
Glama
Sign In

POAScan

by io.github.jakegallen
OverviewDiscussionsAdmin

Close record hash

get_epoch_record
Read-onlyIdempotent

One close record's canonical sha256 (RFC 8785 JCS, UTF-8), byte size and headline counts, plus the URL of the full record mirror. Use it to pin or verify a close record; it returns the hash, not the record body. For readable close stats use get_epoch.

Input Schema

NameRequiredDescriptionDefault
epochNoclosed epoch number; omit for the latest close
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. Changed1 schema field changed
    • addedInput schema / properties / segment
      Added value: +{
+  "description": "chain 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",
+  "minimum": 1,
+  "type": "integer"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / epoch / description
      Added value: +"closed epoch number; omit for the latest close"
  3. Added

TDQS

A4.4/5.0
Behavior4/5

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

Adds real value beyond the annotations by defining the output boundary: it returns a hash plus a mirror URL, not the record body. That prevents a costly mis-call that readOnlyHint alone would not. It stops short of covering auth, rate limits, or what happens for an unknown epoch.

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, front-loaded with the payload contents followed by the usage rule and the sibling redirect. No filler.

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?

With no output schema, the description enumerates the return fields, which is exactly the needed compensation for a two-optional-parameter read tool. Minor gaps remain: "headline counts" is undefined and failure behavior for a nonexistent epoch is unstated.

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%, so both parameters (epoch, segment) are fully documented in the schema, including the segment-repeats-at-genesis-cut caveat. The description adds nothing about parameter meaning, which is the expected baseline here.

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 resource and precise contents: canonical sha256 (RFC 8785 JCS, UTF-8), byte size, headline counts, and mirror URL. It also explicitly differentiates itself from get_epoch ("returns the hash, not the record body"), so an agent can pick between them without reading the schemas.

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 a concrete invocation context ("Use it to pin or verify a close record") and names the alternative for the other use case ("For readable close stats use get_epoch"). Both the when and the when-not are stated outright.

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