Synthex Forge — x402 Paid Agent Services

Ingest Evidence

ingest_evidence

Destructive

Sealing one evidence record into a tamper-evident vault entry. use it rather than create_audit_evidence_package for evidence, not audit evidence package; an object with 24 fields including _raw, action. $0.2 USDC.

Input Schema

Name	Required	Description
`action`	No	The action being recorded or evaluated.
`metadata`	No	Free-form metadata recorded with the result.
`actor_did`	No	The actor did this operation operates on. See the schema for its type and whether it is required.
`timestamp`	No	The timestamp this operation operates on. See the schema for its type and whether it is required.
`policy_ref`	No	Identifier of the policy the decision is bound to.
`action_hash`	No	The action hash this operation operates on. See the schema for its type and whether it is required.

Output Schema

Name	Required	Description
`_raw`	No	The `_raw` field of the response.
`kind`	No	The `kind` field of the response.
`note`	No	A note on how the answer was produced.
`action`	No	The `action` field of the response.
`detail`	Yes	Human-readable explanation of the verdict.
`sealed`	No	The `sealed` field of the response.
`sha256`	No	The `sha256` field of the response.
`entryId`	No	The `entryId` field of the response.
`verdict`	Yes	The decision this tool returned.
`actorDid`	No	The `actorDid` field of the response.
`metadata`	No	The `metadata` field of the response.
`signedBy`	No	The `signedBy` field of the response.
`algorithm`	No	The `algorithm` field of the response.
`policyRef`	No	The `policyRef` field of the response.
`actionHash`	No	The `actionHash` field of the response.
`ed25519Sig`	No	The `ed25519Sig` field of the response.
`recordedAt`	No	The `recordedAt` field of the response.
`observations`	No	The `observations` field of the response.
`publicKeyHex`	No	The `publicKeyHex` field of the response.
`verdictLevel`	No	The `verdictLevel` field of the response.
`eventTimestamp`	No	The `eventTimestamp` field of the response.
`canonicalSha256`	No	The `canonicalSha256` field of the response.
`reproducibility`	No	The `reproducibility` field of the response.
`actionHashDerived`	No	The `actionHashDerived` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed26 schema fields changedOct 31, 2026

addedOutput schema / properties / _raw

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

addedOutput schema / properties / action

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

addedOutput schema / properties / actionHash

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

addedOutput schema / properties / actionHashDerived

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

addedOutput schema / properties / actorDid

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

addedOutput schema / properties / algorithm

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

addedOutput schema / properties / canonicalSha256

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

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

addedOutput schema / properties / eventTimestamp

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

addedOutput schema / properties / kind

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

addedOutput schema / properties / metadata

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

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

addedOutput schema / properties / publicKeyHex

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

addedOutput schema / properties / recordedAt

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

addedOutput schema / properties / reproducibility

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

addedOutput schema / properties / sealed

Added value: +{
+  "description": "The `sealed` 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"
+}

removedOutput schema / properties / status

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

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 / required

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

AddedOct 31, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare the tool as non-read-only, destructive, and non-idempotent, so the safety profile is covered. The description adds useful context: tamper-evident vault entry, single-record sealing, and a specific cost of $0.2 USDC.

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 purpose is front-loaded and the description is short, but it contains an awkward run-on fragment: 'an object with 24 fields including _raw, action.' Because an output schema exists, this return-shape note is unnecessary and reduces clarity.

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 the full schema coverage, annotations, and output schema, the description provides enough context to call the tool: purpose, alternative, cost, and tamper-evident behavior. Minor missing details like permission requirements or irreversibility are not critical here.

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 six parameters. The description adds no parameter-level detail beyond a passing mention of 'action' and `_raw`, which do not clarify the input parameters.

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 action and resource: 'Sealing one evidence record into a tamper-evident vault entry.' It also distinguishes the tool from the sibling `create_audit_evidence_package`, though the wording is somewhat garbled.

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 routes the agent away from `create_audit_evidence_package` for evidence use, giving a clear alternative and condition. It does not cover other possible alternatives, but the main selection guidance is present.

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.