SITEBORNE Utility Network

Verify agent output (v3 candidate)

siteborne_verify_agent_output_v3_candidate

Idempotent

Evaluate a supplied agent output against explicit claims, deterministic requirements, a required JSON Schema, and optional evidence. Use when: the caller already has an output and needs a governed verification verdict. Do not use when: evidence must first be gathered from a company (use siteborne_build_company_evidence_graph), URL (use siteborne_retrieve_verified_web_context), or document (use siteborne_extract_document_evidence_json), or independent reproduction of the output is required (not available). Parameters: verification_mode must be standard; independent_reproduction is defined but unavailable and is rejected before any payment challenge, never downgraded to standard. required_schema must fit SITEBORNE JSON Schema Profile 1 or the request is rejected before payment; minimum_score sets the acceptance threshold; maximum_authorized_price only constrains payment and never relaxes verification policy. Behavior: closed-world: standard mode evaluates only the supplied claims, requirements, output and evidence with no outbound retrieval, and persists governed payment, audit, job and Workflow state; an unpaid request returns payment_required; a repeated identical request with the same payment is replay-protected and is not charged twice. The verification policy and verdict rules do not depend on price or maximum_authorized_price. This service is currently production-disabled and rejects execution. Economics: exact price of $0.017 USD per request in standard mode; the payment challenge requires that amount and the charge settles at exactly that amount. independent_reproduction mode has a governed price of $0.049 USD but is not available: it is rejected before any payment challenge and never substituted. Failure: an unsupported or oversized required_schema, schema-invalid input and unavailable modes are rejected before any payment challenge; a failed verification is a normal fail or conditional verdict, not an error. Returns: claim-level and deterministic-check results, an overall verification verdict, and PCC evidence—not newly gathered source content.

Input Schema

TableJSON Schema

Name	Required	Description
`minimum_score`	No	Minimum overall verification score from 0 through 1; raising it makes the final acceptance verdict stricter.
`required_schema`	Yes	JSON Schema the candidate output must satisfy; it constrains validation and cannot change SITEBORNE verifier policy.
`candidate_output`	Yes	Agent-produced JSON object to evaluate, bounded to 200 properties and depth 10; it is evidence under test, not trusted policy.
`supplied_evidence`	No	Up to twenty evidence objects supplied with the candidate output and bound to integrity hashes.
`verification_mode`	Yes	Verification mode. Only standard (deterministic checks of the supplied material, no outbound retrieval) is available. independent_reproduction has a governed price but is not available: it is rejected with verification_mode_unavailable before any payment challenge and is never downgraded to standard.
`verification_contract`	Yes	Complete set of claims and deterministic checks against which the supplied candidate output is evaluated.
`freshness_requirements`	No	Optional maximum-age limits for evidence and schemas, each expressed in seconds.
`allowed_evidence_sources`	No	Up to ten permitted evidence source URIs; evidence outside this allowlist cannot satisfy source restrictions.
`maximum_authorized_price`	No	Buyer’s decimal-safe maximum authorized price; constrains the payment requirement and never relaxes verification policy.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes	Output schema for verify_agent_output.v1 service. Must be a valid PCC 1.0.0 document with required net.siteborne.agent-verification.v1 extension. Governed candidate output for Service Contract 3.0.0 / PCC 2.0.0.

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 24, 2026

TDQS

A4.8/5.0

Behavior5/5

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

The description goes well beyond the annotations: it discloses closed-world behavior, persistence of payment/audit/job/Workflow state, replay protection, production-disabled status, exact pricing, and the rule that price never relaxes verification policy. All of this is consistent with readOnlyHint=false, openWorldHint=false, idempotentHint=true, and destructiveHint=false.

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 description is well-structured with labeled sections and front-loaded purpose, but it is long and repeats key facts (independent_reproduction unavailability, price independence) in multiple sections. The redundancy is tolerable for a complex paid service, but not every sentence is strictly necessary.

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?

For a complex, paid, production-disabled verification service with 9 parameters and an output schema, the description covers selection, parameter constraints, behavior, failure modes, economics, and return value shape. Nothing an agent needs to decide whether and how to call it is missing.

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 100%, so the baseline is 3; the description adds meaningful constraints not in the schema, such as required_schema needing to fit SITEBORNE JSON Schema Profile 1 and unsupported/oversized schemas being rejected before payment. It also clarifies that verification_mode must be standard and independent_reproduction is never downgraded, though some of this repeats schema text.

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 specific verb and resource—'Evaluate a supplied agent output against explicit claims, deterministic requirements, a required JSON Schema, and optional evidence'—and immediately distinguishes this verification service from sibling evidence-gathering tools by naming them. The scope is unambiguous even without opening the schema.

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?

It provides explicit 'Use when' and 'Do not use when' guidance, names the exact sibling tools for evidence gathering, and states that independent reproduction is unavailable. This gives an agent a clear decision procedure for selecting this tool.

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

All SITEBORNE Utility Network 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.

Resources

Need Help?