Skip to main content
Glama

SCRIPTMASTERLABS — Agent Verify

Proof Check (paid, signed report)

proof_check

Signed proof report for an agent: Proof Score per category, record count, settled value, buyer diversity. PAID via x402 v2 (exact scheme: USDC on Base, USDC on Solana, XRP on XRPL, USDC on Arc, or XAH on Xahau — same USD price on every route). Call without payment_signature to receive the payment requirements (no charge); call again with payment_signature = the base64 PAYMENT-SIGNATURE for one of those accepts. Settles once per signature (replays return 409); the report is returned only after settlement. Errors: 503 closed, 402 invalid/mismatched payment, 502 facilitator unavailable.

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": {
      "agent": "<agent>"
    },
    "name": "proof_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentYesAgent identity: 0x address, did:pkh:eip155:<chain>:0x… or did:ethr:0x…
payment_signatureNobase64 x402 v2 PAYMENT-SIGNATURE

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, it discloses the paid x402 v2 flow, the five payment routes, that settlement precedes report delivery, that signatures settle once and replays return 409, and the meaning of 503/402/502 failures. This is consistent with idempotentHint=false and adds substantial operational context an agent cannot infer from the annotations alone.

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?

Front-loaded with the payoff (what the report contains), then payment mechanics, then errors — a logical order with almost no filler. The long parenthetical route list is necessary information but slightly dense, keeping it short of a 5.

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?

With no output schema, the description compensates by naming the report fields, and it covers the non-obvious payment protocol and error taxonomy. For a 2-parameter paid tool, an agent has everything needed to call it correctly on first attempt.

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 already 100%, so the baseline is 3, but the description adds real meaning: payment_signature must be the base64 PAYMENT-SIGNATURE for one of the advertised accepts, and omitting it is a free requirements-fetch rather than an error. That is a call-pattern insight the schema alone does not convey.

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?

The description opens with a concrete verb+resource ('Signed proof report for an agent') and enumerates the returned fields (Proof Score per category, record count, settled value, buyer diversity), which clearly separates it from siblings like proof_index or proof_verify_record that also touch proofs.

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 gives an explicit two-step invocation protocol: call without payment_signature to get payment requirements (no charge), then call again with a signature from one of the accepted routes. It doesn't explicitly say when to prefer proof_index or proof_verify_record, but the paid-report framing makes the intended context clear.

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