Skip to main content
Glama

SCRIPTMASTERLABS — Agent Verify

Latest Proof Records

ledger_list
Read-onlyIdempotent

List the latest Proof Records from the ledger, newest first, together with the current ledger head. Every record is a paid agent job that was escrowed on Circle Arc (chain 5042), accepted by the buyer's EIP-191 signature, released on-chain and independently re-verified. Page backwards through history with before_seq and cap the page size with limit. Free, read-only.

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": "ledger_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPage size: maximum number of records to return, newest first (1-500, default 20).
before_seqNoPagination cursor: return only records whose ledger sequence number is below this value; pass the oldest seq from the previous page to page backwards.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / before_seq / description
      Added value: +"Pagination cursor: return only records whose ledger sequence number is below this value; pass the oldest seq from the previous page to page backwards."
    • addedInput schema / properties / limit / description
      Added value: +"Page size: maximum number of records to return, newest first (1-500, default 20)."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, but the description adds genuinely new behavioral context: the default newest-first ordering, the inclusion of the ledger head in the response, and the provenance/trust chain behind each record (escrowed on Circle Arc chain 5042, EIP-191 buyer signature, on-chain release, independent re-verification). It does not discuss rate limits or response field shape, but the safety profile is already covered.

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?

Front-loaded with purpose, then pagination controls, then trust/cost context. Four sentences, no filler, and the most decision-relevant information (what you get, how to page) comes first.

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 usefully signals that the response bundles records plus the ledger head, but it never sketches what a record contains beyond its trust properties. For a read-only two-parameter list tool this is nearly complete, with only the return payload shape left implicit.

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 both parameters are already fully documented including the 1-500 range, default of 20, and the 'oldest seq from previous page' cursor convention. The description restates that pagination pattern without adding syntax or edge cases beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource ('List the latest Proof Records from the ledger'), adds the ordering ('newest first') and a secondary return element ('the current ledger head'). It does not name or contrast any sibling (e.g. proof_index or agent_records), so an agent must infer differentiation from names alone.

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

Usage Guidelines3/5

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

Explains the mechanics of backward pagination ('page backwards through history with before_seq') and the cost model ('Free, read-only'), which implies when this is safe to call. It gives no explicit when-to-use vs when-not guidance, nor any alternative tool for filtering or verification.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources