Skip to main content
Glama

Synthex Forge — x402 Paid Agent Services

Verify Tool Output

verify_tool_output
Read-onlyIdempotent

Whether an output actually satisfies its schema, claims and staleness. use it rather than assess_tool_verdict for output, not verdict; an object with 57 fields including agedSeconds, algorithm. $0.5 USDC.

Input Schema

NameRequiredDescriptionDefault
checksNoWhich checks to run. Omit for the default set.
outputNoThe output this operation operates on. See the schema for its type and whether it is required.
schemaNoThe JSON Schema the operation operates on.
claimedNoThe claim being made.
subjectNoThe subject the operation is applied to — an id, a URL or a name, depending on the operation.
accuracyNoThe accuracy this operation operates on. See the schema for its type and whether it is required.
stalenessBudgetSecondsNoThe stalenessBudgetSeconds this operation operates on. See the schema for its type and whether it is required.

Output Schema

NameRequiredDescriptionDefault
keyNoThe `key` field of the response.
maxNoThe `max` field of the response.
minNoThe `min` field of the response.
axisNoThe `axis` field of the response.
kindNoThe `kind` field of the response.
modeNoThe `mode` field of the response.
noteNoA note on how the answer was produced.
pathNoThe `path` field of the response.
tierNoThe `tier` field of the response.
totalNoThe `total` field of the response.
clauseNoThe `clause` field of the response.
countsNoThe `counts` field of the response.
detailYesHuman-readable explanation of the verdict.
perLegNoThe `perLeg` field of the response.
sha256NoThe `sha256` field of the response.
usableNoThe `usable` field of the response.
findingNoThe `finding` field of the response.
framingNoThe `framing` field of the response.
matchesNoThe `matches` field of the response.
metricsNoThe `metrics` field of the response.
scopingNoThe `scoping` field of the response.
skippedNoThe `skipped` field of the response.
subjectNoThe `subject` field of the response.
verdictYesThe decision this tool returned.
findingsNoThe `findings` field of the response.
severityNoThe `severity` field of the response.
signedByNoThe `signedBy` field of the response.
algorithmNoThe `algorithm` field of the response.
checksRunNoThe `checksRun` field of the response.
fetchedAtNoThe `fetchedAt` field of the response.
stored_atNoThe `stored_at` field of the response.
assessableNoThe `assessable` field of the response.
ed25519SigNoThe `ed25519Sig` field of the response.
mismatchesNoThe `mismatches` field of the response.
overBudgetNoThe `overBudget` field of the response.
verifiedAtNoThe `verifiedAt` field of the response.
agedSecondsNoThe `agedSeconds` field of the response.
series_rowsNoThe `series_rows` field of the response.
coverageGapsNoThe `coverageGaps` field of the response.
evidenceCoreNoThe `evidenceCore` field of the response.
observationsNoThe `observations` field of the response.
outputSha256NoThe `outputSha256` field of the response.
paths_at_maxNoThe `paths_at_max` field of the response.
paths_at_minNoThe `paths_at_min` field of the response.
publicKeyHexNoThe `publicKeyHex` field of the response.
verdictLevelNoThe `verdictLevel` field of the response.
coverage_gapsNoThe `coverage_gaps` field of the response.
hash_bound_okNoThe `hash_bound_ok` field of the response.
attestation_idNoThe `attestation_id` field of the response.
evidenceDigestNoThe `evidenceDigest` field of the response.
reference_rowsNoThe `reference_rows` field of the response.
canonicalSha256NoThe `canonicalSha256` field of the response.
hash_bound_failNoThe `hash_bound_fail` field of the response.
reproducibilityNoThe `reproducibility` field of the response.
standardVersionNoThe `standardVersion` field of the response.
verificationHintNoThe `verificationHint` field of the response.
stalenessBudgetSecondsNoThe `stalenessBudgetSeconds` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed59 schema fields changed
    • addedOutput schema / properties / agedSeconds
      Added value: +{
      +  "description": "The `agedSeconds` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / algorithm
      Added value: +{
      +  "description": "The `algorithm` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / assessable
      Added value: +{
      +  "description": "The `assessable` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / attestation_id
      Added value: +{
      +  "description": "The `attestation_id` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / axis
      Added value: +{
      +  "description": "The `axis` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / canonicalSha256
      Added value: +{
      +  "description": "The `canonicalSha256` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / checksRun
      Added value: +{
      +  "description": "The `checksRun` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / clause
      Added value: +{
      +  "description": "The `clause` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / counts
      Added value: +{
      +  "description": "The `counts` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / coverageGaps
      Added value: +{
      +  "description": "The `coverageGaps` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / coverage_gaps
      Added value: +{
      +  "description": "The `coverage_gaps` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / detail
      Added value: +{
      +  "description": "Human-readable explanation of the verdict.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / ed25519Sig
      Added value: +{
      +  "description": "The `ed25519Sig` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / evidenceCore
      Added value: +{
      +  "description": "The `evidenceCore` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / evidenceDigest
      Added value: +{
      +  "description": "The `evidenceDigest` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / fetchedAt
      Added value: +{
      +  "description": "The `fetchedAt` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / finding
      Added value: +{
      +  "description": "The `finding` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / findings
      Added value: +{
      +  "description": "The `findings` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / framing
      Added value: +{
      +  "description": "The `framing` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / hash_bound_fail
      Added value: +{
      +  "description": "The `hash_bound_fail` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / hash_bound_ok
      Added value: +{
      +  "description": "The `hash_bound_ok` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / key
      Added value: +{
      +  "description": "The `key` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / kind
      Added value: +{
      +  "description": "The `kind` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / matches
      Added value: +{
      +  "description": "The `matches` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / max
      Added value: +{
      +  "description": "The `max` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / metrics
      Added value: +{
      +  "description": "The `metrics` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / min
      Added value: +{
      +  "description": "The `min` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / mismatches
      Added value: +{
      +  "description": "The `mismatches` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / mode
      Added value: +{
      +  "description": "The `mode` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / note
      Added value: +{
      +  "description": "A note on how the answer was produced.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / observations
      Added value: +{
      +  "description": "The `observations` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / outputSha256
      Added value: +{
      +  "description": "The `outputSha256` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / overBudget
      Added value: +{
      +  "description": "The `overBudget` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / path
      Added value: +{
      +  "description": "The `path` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / paths_at_max
      Added value: +{
      +  "description": "The `paths_at_max` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / paths_at_min
      Added value: +{
      +  "description": "The `paths_at_min` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / perLeg
      Added value: +{
      +  "description": "The `perLeg` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / publicKeyHex
      Added value: +{
      +  "description": "The `publicKeyHex` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / reference_rows
      Added value: +{
      +  "description": "The `reference_rows` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / reproducibility
      Added value: +{
      +  "description": "The `reproducibility` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / scoping
      Added value: +{
      +  "description": "The `scoping` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / series_rows
      Added value: +{
      +  "description": "The `series_rows` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / severity
      Added value: +{
      +  "description": "The `severity` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / sha256
      Added value: +{
      +  "description": "The `sha256` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / signedBy
      Added value: +{
      +  "description": "The `signedBy` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / skipped
      Added value: +{
      +  "description": "The `skipped` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / stalenessBudgetSeconds
      Added value: +{
      +  "description": "The `stalenessBudgetSeconds` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / standardVersion
      Added value: +{
      +  "description": "The `standardVersion` field of the response.",
      +  "type": "object"
      +}
    • removedOutput schema / properties / status
      Removed value: -{
      -  "type": "string"
      -}
    • addedOutput schema / properties / stored_at
      Added value: +{
      +  "description": "The `stored_at` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / subject
      Added value: +{
      +  "description": "The `subject` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / tier
      Added value: +{
      +  "description": "The `tier` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / total
      Added value: +{
      +  "description": "The `total` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / usable
      Added value: +{
      +  "description": "The `usable` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / verdict
      Added value: +{
      +  "description": "The decision this tool returned.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / verdictLevel
      Added value: +{
      +  "description": "The `verdictLevel` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / verificationHint
      Added value: +{
      +  "description": "The `verificationHint` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / verifiedAt
      Added value: +{
      +  "description": "The `verifiedAt` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / required
      Added value: +[
      +  "detail",
      +  "verdict"
      +]
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds useful behavioral context: it verifies schema conformance, claims, and staleness, mentions payment cost, and notes the return object is large with fields such as `agedSeconds` and `algorithm`.

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 short and front-loads the core purpose and differentiation. However, the grammar is awkward in places ('use it rather than...'), and the note about the 57-field return object is arguably redundant because an output schema already exists.

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?

Given rich structured metadata, including full schema coverage, annotations, and an output schema, the description is largely complete for selecting and invoking the tool. It could be stronger with a clearer enumeration of checks or subject/accuracy behavior, but the essentials are present.

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%, so the schema already documents all seven parameters. The description gestures at schema, claims, and staleness, but does not add meaningful semantics for parameters such as `checks`, `subject`, or `accuracy` beyond what the schema provides.

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 identifies a specific verification operation for output and explicitly contrasts it with `assess_tool_verdict` by saying 'for output, not verdict.' The meaning is clear, though the opening is an incomplete fragment ('Whether an output...') rather than a direct verb phrase.

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 a direct routing rule: use this rather than `assess_tool_verdict` when dealing with output rather than a verdict. That is a clear alternative and exclusion, but it does not cover other potentially adjacent verification tools.

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.