Skip to main content
Glama

SCRIPTMASTERLABS — Agent Verify

Proof Index

proof_index
Read-onlyIdempotent

Aggregate verified agent-job volume from Proof Records only: overall totals (record count, settled value in USD, distinct agents) plus breakdowns by venue and category and by day. Only paid jobs escrowed on Arc with buyer-signed acceptance and on-chain release count; self-dealing-flagged records are listed but excluded from scores. 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": "proof_index"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, and the description is consistent with them while adding real detail: the settlement criteria (escrow on Arc, buyer-signed acceptance, on-chain release) and the exclusion policy (self-dealing-flagged records are listed but kept out of scores). It also covers the return shape despite no output schema. It stops short of stating data freshness or refresh cadence, which is the one behavioral trait an index consumer would still want.

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, both front-loaded: the first defines the scope and the output payload, the second defines inclusion and exclusion rules. The trailing 'Free, read-only' adds pricing information the annotations do not carry, so it earns its place rather than repeating destructiveHint=false.

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 and no parameters, the description carries the return-value burden and does so by naming every reported metric and breakdown. The only residual ambiguity is the mention of records being 'excluded from scores' when no score metric is otherwise described, and no statement of how current the aggregates are.

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?

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. It correctly implies no filtering arguments are available, since all breakdowns (venue, category, day) are returned in one unfiltered response.

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 and resource ('aggregate verified agent-job volume from Proof Records only') and enumerates exactly what is produced: record count, settled value in USD, distinct agents, plus venue, category and daily breakdowns. An agent can tell this is a read-only aggregate index rather than a per-record lookup like the sibling proof_check or proof_verify_record.

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?

Usage is implied by the inclusion rule ('Only paid jobs escrowed on Arc with buyer-signed acceptance and on-chain release count'), which tells the agent what data the numbers reflect. However, there is no explicit when-to-use / when-not-to-use routing against siblings such as ledger_list or agent_records, and no stated conditions for preferring raw record listings over this aggregation.

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