Synthex Forge — x402 Paid Agent Services

Issue Readiness Attestation

issue_readiness_attestation

Destructive

Readiness Attest. use it rather than issue_attestation for readiness attestation, not attestation; an object with 29 fields including algorithm, attestedAt. $0.25 USDC.

Input Schema

Name	Required	Description
`target`	No	The target the operation acts on — a host, a service or an endpoint.
`custodian`	No	The custodian this operation operates on. See the schema for its type and whether it is required.
`policy_snapshot`	No	The policy snapshot this operation operates on. See the schema for its type and whether it is required.
`readiness_evidence`	No	The readiness evidence this operation operates on. See the schema for its type and whether it is required.

Output Schema

Name	Required	Description
`kind`	No	The `kind` field of the response.
`note`	No	A note on how the answer was produced.
`detail`	Yes	Human-readable explanation of the verdict.
`policy`	No	The `policy` field of the response.
`schema`	No	The `schema` field of the response.
`sha256`	No	The `sha256` field of the response.
`target`	No	The `target` field of the response.
`receipt`	No	The `receipt` field of the response.
`signals`	No	The `signals` field of the response.
`verdict`	Yes	The decision this tool returned.
`boundary`	No	The `boundary` field of the response.
`evidence`	No	The `evidence` field of the response.
`signedBy`	No	The `signedBy` field of the response.
`algorithm`	No	The `algorithm` field of the response.
`attestsAt`	No	The `attestsAt` field of the response.
`custodian`	No	The `custodian` field of the response.
`signature`	Yes	The Ed25519 signature over the evidence core, base64-encoded.
`typedCore`	No	The `typedCore` field of the response.
`verify_at`	No	The `verify_at` field of the response.
`attestedAt`	No	The `attestedAt` field of the response.
`disclaimer`	No	The `disclaimer` field of the response.
`observations`	No	The `observations` field of the response.
`publicKeyHex`	No	The `publicKeyHex` field of the response.
`deterministic`	No	The `deterministic` field of the response.
`canonicalSha256`	No	The `canonicalSha256` field of the response.
`reproducibility`	No	The `reproducibility` field of the response.
`verificationHint`	No	The `verificationHint` field of the response.
`noKillSwitchAuthority`	No	The `noKillSwitchAuthority` field of the response.
`readinessIsSuppliedEvidence`	No	The `readinessIsSuppliedEvidence` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed31 schema fields changedOct 31, 2026

addedOutput schema / properties / algorithm

Added value: +{
+  "description": "The `algorithm` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / attestedAt

Added value: +{
+  "description": "The `attestedAt` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / attestsAt

Added value: +{
+  "description": "The `attestsAt` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / boundary

Added value: +{
+  "description": "The `boundary` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / canonicalSha256

Added value: +{
+  "description": "The `canonicalSha256` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / custodian

Added value: +{
+  "description": "The `custodian` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / detail

Added value: +{
+  "description": "Human-readable explanation of the verdict.",
+  "type": "string"
+}

addedOutput schema / properties / deterministic

Added value: +{
+  "description": "The `deterministic` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / disclaimer

Added value: +{
+  "description": "The `disclaimer` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / evidence

Added value: +{
+  "description": "The `evidence` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / kind

Added value: +{
+  "description": "The `kind` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / noKillSwitchAuthority

Added value: +{
+  "description": "The `noKillSwitchAuthority` 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 / policy

Added value: +{
+  "description": "The `policy` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / publicKeyHex

Added value: +{
+  "description": "The `publicKeyHex` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / readinessIsSuppliedEvidence

Added value: +{
+  "description": "The `readinessIsSuppliedEvidence` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / receipt

Added value: +{
+  "description": "The `receipt` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / reproducibility

Added value: +{
+  "description": "The `reproducibility` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / schema

Added value: +{
+  "description": "The `schema` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / sha256

Added value: +{
+  "description": "The `sha256` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / signals

Added value: +{
+  "description": "The `signals` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / signature

Added value: +{
+  "description": "The Ed25519 signature over the evidence core, base64-encoded.",
+  "type": "string"
+}

addedOutput schema / properties / signedBy

Added value: +{
+  "description": "The `signedBy` field of the response.",
+  "type": "object"
+}

removedOutput schema / properties / status

Removed value: -{
-  "type": "string"
-}

addedOutput schema / properties / target

Added value: +{
+  "description": "The `target` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / typedCore

Added value: +{
+  "description": "The `typedCore` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / verdict

Added value: +{
+  "description": "The decision this tool returned.",
+  "type": "string"
+}

addedOutput schema / properties / verificationHint

Added value: +{
+  "description": "The `verificationHint` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / verify_at

Added value: +{
+  "description": "The `verify_at` field of the response.",
+  "type": "object"
+}

addedOutput schema / required

Added value: +[
+  "detail",
+  "signature",
+  "verdict"
+]

AddedOct 31, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already disclose that this is destructive and non-idempotent. The description adds useful context that it costs $0.25 USDC and returns an object with 29 fields, but it does not explain what state is destroyed or what permissions are required, leaving the destructive behavior opaque.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short, but it begins with a sentence fragment and chains together the routing hint, output shape, and price in one awkward run. It is not bloated, but the front-loading is weak and the structure is hard to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the description need not explain return fields in detail, and annotations cover the safety profile. However, for a destructive attestation issuance, the description still leaves the core operation and its prerequisites under-explained.

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 four parameters. The description mentions no input parameters at all; its only field list refers to the output object, so it adds nothing beyond the schema for parameter semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with 'Readiness Attest.', which essentially restates the tool name and title rather than stating a specific verb and resource. It adds a routing hint versus `issue_attestation`, but never explains what a readiness attestation actually is or does.

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 explicitly says to use this tool rather than `issue_attestation` for readiness attestation, and clarifies that it is not for general attestation. The condition is clear, though other sibling attestation tools are not mentioned.

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

All Synthex Forge — x402 Paid Agent Services 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.