Synthex Forge — x402 Paid Agent Services

Create Audit Evidence Package

create_audit_evidence_package

Destructive

Assemble and sign ONE self-contained. use it rather than create_signed_research_brief for audit evidence package, not signed research brief; an object with 56 fields including artifactDigest, artifact_count. $4 USDC.

Input Schema

Name	Required	Description
`as_of`	No	The date the answer is computed as of (YYYY-MM-DD). Defaults to today. Use it to reproduce a past answer exactly.
`period`	No	The reporting period the answer covers.
`policy`	No	The policy document or policy id the decision is evaluated against.
`subject`	No	The subject the operation is applied to — an id, a URL or a name, depending on the operation.
`artifacts`	No	The artifacts this operation operates on. See the schema for its type and whether it is required.
`assertions`	No	The assertions this operation operates on. See the schema for its type and whether it is required.
`attestations`	No	The attestations this operation operates on. See the schema for its type and whether it is required.

Output Schema

Name	Required	Description
`id`	No	The `id` field of the response.
`asOf`	No	The `asOf` field of the response.
`gaps`	No	The `gaps` field of the response.
`kind`	No	The `kind` field of the response.
`note`	No	A note on how the answer was produced.
`root`	No	The `root` field of the response.
`as_of`	No	The date the answer is computed as of.
`basis`	No	The `basis` field of the response.
`count`	No	The `count` field of the response.
`index`	No	The `index` field of the response.
`notes`	No	The `notes` field of the response.
`checks`	No	The individual checks that were run.
`detail`	Yes	Human-readable explanation of the verdict.
`digest`	No	The `digest` field of the response.
`graded`	No	The `graded` field of the response.
`period`	No	The `period` field of the response.
`policy`	No	The `policy` field of the response.
`sha256`	No	The `sha256` field of the response.
`signed`	No	The `signed` field of the response.
`status`	No	The status of the operation.
`content`	No	The `content` field of the response.
`subject`	No	The `subject` field of the response.
`excluded`	No	The `excluded` field of the response.
`included`	No	The `included` field of the response.
`problems`	No	The `problems` field of the response.
`signedBy`	No	The `signedBy` field of the response.
`statuses`	No	The `statuses` field of the response.
`supplied`	No	The `supplied` field of the response.
`artifacts`	No	The `artifacts` field of the response.
`assertion`	No	The `assertion` field of the response.
`signature`	Yes	The Ed25519 signature over the evidence core, base64-encoded.
`signed_at`	No	The `signed_at` field of the response.
`stored_at`	No	The `stored_at` field of the response.
`contentRef`	No	The `contentRef` field of the response.
`ed25519Sig`	No	The `ed25519Sig` field of the response.
`merkleRoot`	No	The `merkleRoot` field of the response.
`package_id`	No	The `package_id` field of the response.
`provenance`	No	The `provenance` field of the response.
`content_ref`	No	The `content_ref` field of the response.
`digestMatch`	No	The `digestMatch` field of the response.
`merkle_root`	No	The `merkle_root` field of the response.
`attestations`	No	The `attestations` field of the response.
`evidenceCore`	No	The `evidenceCore` field of the response.
`sharedTokens`	No	The `sharedTokens` field of the response.
`merkle_leaves`	No	The `merkle_leaves` field of the response.
`merkle_proofs`	No	The `merkle_proofs` field of the response.
`artifactDigest`	No	The `artifactDigest` field of the response.
`artifact_count`	No	The `artifact_count` field of the response.
`declaredDigest`	No	The `declaredDigest` field of the response.
`profileVersion`	No	Version of the answer profile.
`artifact_digest`	No	The `artifact_digest` field of the response.
`profile_version`	No	Version of the answer profile.
`matchedArtifacts`	No	The `matchedArtifacts` field of the response.
`assertion_results`	No	The `assertion_results` field of the response.
`merkle_leaf_index`	No	The `merkle_leaf_index` field of the response.
`supplied_artifact_count`	No	The `supplied_artifact_count` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed57 schema fields changedOct 31, 2026

addedOutput schema / properties / artifactDigest

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

addedOutput schema / properties / artifact_count

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

addedOutput schema / properties / artifact_digest

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

addedOutput schema / properties / artifacts

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

addedOutput schema / properties / asOf

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

addedOutput schema / properties / as_of

Added value: +{
+  "description": "The date the answer is computed as of.",
+  "type": "string"
+}

addedOutput schema / properties / assertion

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

addedOutput schema / properties / assertion_results

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

addedOutput schema / properties / attestations

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

addedOutput schema / properties / basis

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

addedOutput schema / properties / checks

Added value: +{
+  "description": "The individual checks that were run.",
+  "items": {
+    "description": "One record.",
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / content

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

addedOutput schema / properties / contentRef

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

addedOutput schema / properties / content_ref

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

addedOutput schema / properties / count

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

addedOutput schema / properties / declaredDigest

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

addedOutput schema / properties / detail

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

addedOutput schema / properties / digest

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

addedOutput schema / properties / digestMatch

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

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

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

addedOutput schema / properties / gaps

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

addedOutput schema / properties / graded

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

addedOutput schema / properties / id

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

addedOutput schema / properties / included

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

addedOutput schema / properties / index

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

addedOutput schema / properties / kind

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

addedOutput schema / properties / matchedArtifacts

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

addedOutput schema / properties / merkleRoot

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

addedOutput schema / properties / merkle_leaf_index

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

addedOutput schema / properties / merkle_leaves

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

addedOutput schema / properties / merkle_proofs

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

addedOutput schema / properties / merkle_root

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

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

addedOutput schema / properties / package_id

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

addedOutput schema / properties / period

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

addedOutput schema / properties / policy

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

addedOutput schema / properties / problems

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

addedOutput schema / properties / profileVersion

Added value: +{
+  "description": "Version of the answer profile.",
+  "type": "string"
+}

addedOutput schema / properties / profile_version

Added value: +{
+  "description": "Version of the answer profile.",
+  "type": "string"
+}

addedOutput schema / properties / provenance

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

addedOutput schema / properties / root

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

addedOutput schema / properties / sha256

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

addedOutput schema / properties / sharedTokens

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

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

addedOutput schema / properties / signedBy

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

addedOutput schema / properties / signed_at

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

addedOutput schema / properties / status / description
```
Added value: +"The status of the operation."
```

addedOutput schema / properties / statuses

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

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

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

addedOutput schema / properties / supplied_artifact_count

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

addedOutput schema / required

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

AddedOct 31, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare the write/destructive/non-idempotent profile, so the description doesn't need to restate it. It does add genuinely useful context the annotations lack: the price point ($4 USDC) and the shape of the returned object (56 fields including artifactDigest, artifact_count). However it says nothing about the signing implications, whether artifacts/assertions/attestations are consumed or just referenced, or any irreversibility of the signing step.

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

Conciseness2/5

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

Very short, but the opening clause is a truncated fragment ("ONE self-contained.") and the pricing and return-shape details are jammed into one run-on sentence. Brevity here comes at the cost of comprehensibility rather than through discipline.

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 spelling out the 56 return fields is optional, and the schema fully documents inputs. What remains missing is anything about how the three optional array parameters (artifacts/assertions/attestations) relate to the assembled package, and the broken sentence leaves the tool's actual output semantics unclear despite the price being stated.

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?

With 7 parameters at 100% schema description coverage, the schema carries parameter documentation (as_of, period, policy, subject, artifacts, assertions, attestations). The description adds nothing about any of them, so baseline 3 applies rather than more or less.

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?

States a specific verb+resource ("Assemble and sign ... audit evidence package") and explicitly differentiates from the sibling create_signed_research_brief. The sentence is grammatically broken ("ONE self-contained.") which leaves the object of the verb truncated, but the resource is still recoverable from the name and the following clause.

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?

Explicitly names the alternative (create_signed_research_brief) and states the condition that selects this tool instead: audit evidence package, not signed research brief. No further when-not guidance, but the primary routing decision is covered.

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.