Synthex Forge — x402 Paid Agent Services

Verify Operation Reproducibility

verify_operation_reproducibility

Read-onlyIdempotent

C... use it rather than assess_operation_behaviour_drift for operation reproducibility, not operation behaviour drift; an object with 20 fields including artifact_digest_compared, artifact_digests_compared. $0.25 USDC.

Input Schema

Name	Required	Description
`artifact_sha256`	No	The artifact sha256 this operation operates on. See the schema for its type and whether it is required.
`recorded_context`	No	The recorded context this operation operates on. See the schema for its type and whether it is required.
`reproduction_sha256`	No	The reproduction sha256 this operation operates on. See the schema for its type and whether it is required.
`reproduction_context`	No	The reproduction context this operation operates on. See the schema for its type and whether it is required.

Output Schema

Name	Required	Description
`type`	No	The `type` field of the response.
`detail`	Yes	Human-readable explanation of the verdict.
`inputs`	No	The `inputs` field of the response.
`versions`	No	The `versions` field of the response.
`exception`	No	The `exception` field of the response.
`differences`	No	The `differences` field of the response.
`environment`	No	The `environment` field of the response.
`parts_compared`	No	The `parts_compared` field of the response.
`artifact_sha256`	No	The `artifact_sha256` field of the response.
`recorded_sha256`	No	The `recorded_sha256` field of the response.
`values_compared`	No	The `values_compared` field of the response.
`comparison_clean`	No	The `comparison_clean` field of the response.
`difference_count`	No	The `difference_count` field of the response.
`reproduction_sha256`	No	The `reproduction_sha256` field of the response.
`artifact_digests_match`	No	The `artifact_digests_match` field of the response.
`context_parts_supplied`	No	The `context_parts_supplied` field of the response.
`parts_missing_recorded`	No	The `parts_missing_recorded` field of the response.
`artifact_digest_compared`	No	The `artifact_digest_compared` field of the response.
`artifact_digests_compared`	No	The `artifact_digests_compared` field of the response.
`parts_missing_reproduction`	No	The `parts_missing_reproduction` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed22 schema fields changedOct 31, 2026

addedOutput schema / properties / artifact_digest_compared

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

addedOutput schema / properties / artifact_digests_compared

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

addedOutput schema / properties / artifact_digests_match

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

addedOutput schema / properties / artifact_sha256

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

addedOutput schema / properties / comparison_clean

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

addedOutput schema / properties / context_parts_supplied

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

addedOutput schema / properties / detail

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

addedOutput schema / properties / difference_count

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

addedOutput schema / properties / differences

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

addedOutput schema / properties / environment

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

addedOutput schema / properties / exception

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

addedOutput schema / properties / inputs

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

addedOutput schema / properties / parts_compared

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

addedOutput schema / properties / parts_missing_recorded

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

addedOutput schema / properties / parts_missing_reproduction

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

addedOutput schema / properties / recorded_sha256

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

addedOutput schema / properties / reproduction_sha256

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

removedOutput schema / properties / status

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

addedOutput schema / properties / type

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

addedOutput schema / properties / values_compared

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

addedOutput schema / properties / versions

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

addedOutput schema / required
```
Added value: +[
+  "detail"
+]
```

AddedOct 31, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so safety and repeatability are covered. The description adds genuinely useful non-schema context — a $0.25 USDC cost and the shape of the return (an object with 20 fields including artifact_digest_compared) — but says nothing about what constitutes a pass/fail or what the comparison is against.

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?

The description begins mid-sentence with 'C...' — visibly truncated and not front-loaded with the action. What remains is a single run-on fragment mixing the sibling exclusion, a return-field count, and a price, with no lead sentence stating what the tool does.

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

Completeness2/5

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

An output schema exists, so return values need not be explained, and annotations cover the safety profile. But the core behavior — comparing recorded artifact/context to reproduction artifact/context and how a reproducibility verdict is determined — is absent, and the leading text is corrupted, leaving an agent unable to confidently construct a correct call.

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; baseline 3 applies. The description adds no parameter meaning beyond that, and notably the schema text itself is boilerplate ('See the schema for its type and whether it is required'), so nothing clarifies the recorded-vs-reproduction pairing.

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

Purpose3/5

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

The fragment 'for operation reproducibility, not operation behaviour drift' plus the title name the resource and its scope, but the description opens with a truncated 'C...' and never states a complete verb phrase for what the tool actually does (compare a recorded artifact/context against a reproduction). The distinction from the sibling is the only substantive purpose signal.

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 names the alternative ('use it rather than `assess_operation_behaviour_drift`') and gives the discriminator ('for operation reproducibility, not operation behaviour drift'). No prerequisites or when-not-to-use beyond that single exclusion, so it is not a 5.

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.