Agent Output Verifier by Sarnai

get_verification_record

Read-only

AI agent reputation and trust score: check an AI agent's verification record before you hire it, rely on its output or pay it. Returns its signed verification history: verified, passed and failed counts, last seen, and a recency-weighted score with 95% confidence interval. Check a counterparty before you pay, or see the record buyers will see. AI Agent Scores: $0.01 per lookup when there is a score; a lookup for an AI agent with no history is answered free, signed.

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_id": "<agent_id>"
    },
    "name": "get_verification_record"
  }
}

Input Schema

Name	Required	Description	Default
`agent_id`	Yes	The agent_id whose verification history to score (as passed to /verify/schema): the AI agent that produced the output checked by those calls (for example, the seller). agent_ids starting with 'test-' are reserved for testing and never have a history. Example: example-agent-001. A route template such as {agent_id} or :agent_id is refused with a 400.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026

changedInput schema / properties / agent_id / description

Previous value: -"The agent_id whose verification history to score (as passed to /verify/schema): the AI agent that produced the output checked by those calls (for example, the seller). agent_ids starting with 'test-' are reserved for testing and never have a history."New value: +"The agent_id whose verification history to score (as passed to /verify/schema): the AI agent that produced the output checked by those calls (for example, the seller). agent_ids starting with 'test-' are reserved for testing and never have a history. Example: example-agent-001. A route template such as {agent_id} or :agent_id is refused with a 400."

Changed1 schema field changedOct 14, 2026

changedInput schema / properties / agent_id / description

Previous value: -"The agent_id whose verification history to score (as passed to /verify/schema): the agent that produced the output checked by those calls (for example, the seller). agent_ids starting with 'test-' are reserved for testing and never have a history."New value: +"The agent_id whose verification history to score (as passed to /verify/schema): the AI agent that produced the output checked by those calls (for example, the seller). agent_ids starting with 'test-' are reserved for testing and never have a history."

First observedOct 1, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations already cover safety (readOnlyHint=true, destructiveHint=false, openWorldHint=false), and the description adds genuinely non-structural behavior: the output is 'signed', records are available for agent_ids without history, and pricing is $0.01 per scored lookup while no-history lookups are free. That cost and trust-signing disclosure is exactly the kind of trait an agent cannot get from the annotations or schema.

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 purpose and return contents are front-loaded and each sentence carries information. There is mild redundancy between 'before you ... pay it' and 'Check a counterparty before you pay', which repeats the same trigger twice without new detail.

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, so the description must carry the return value — and it does, enumerating the counts, last-seen timestamp, weighted score and confidence interval. Combined with the pricing note and the single well-documented parameter, an agent has enough to call this 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 description coverage is 100% and the agent_id field already documents the accepted identifier form, the risk of route templates, and the reserved 'test-' prefix. The description adds no further semantics about the parameter, so the baseline of 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?

The description states a specific verb and resource — 'check an AI agent's verification record' and 'AI agent reputation and trust score' — and spells out the returned artifacts (verified/passed/failed counts, last seen, recency-weighted score with a 95% CI). It never names or contrasts the sibling verify_schema, so an agent must infer the boundary itself.

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?

'Check a counterparty before you pay, or see the record buyers will see' gives concrete decision points (hire, rely on output, pay) that trigger the tool. It stops short of explicit exclusions or an explicit handoff rule to verify_schema, so the when-not side is left to inference.

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

All Agent Output Verifier by Sarnai tools Inspect

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.