Synthex Forge — x402 Paid Agent Services

Resolve Data Conflict

resolve_data_conflict

Read-onlyIdempotent

Resolve conflicting claims, or preserve the disagreement. use it rather than create_signed_data_snapshot for conflict, not signed data snapshot; an object with 32 fields including basis, candidates. $0.25 USDC.

Input Schema

Name	Required	Description
`claims`	No	The claims to evaluate, as a list of {subject, predicate, object} or as free text.
`prefer`	No	Which side to prefer when the conflict cannot be resolved.
`subject`	No	The subject the operation is applied to — an id, a URL or a name, depending on the operation.
`recency_breaks_ties`	No	Whether the more recent claim wins a tie.

Output Schema

Name	Required	Description
`left`	No	The `left` field of the response.
`note`	No	A note on how the answer was produced.
`type`	No	The `type` field of the response.
`basis`	No	The `basis` field of the response.
`field`	No	The `field` field of the response.
`quote`	No	The `quote` field of the response.
`right`	No	The `right` field of the response.
`value`	No	The `value` field of the response.
`detail`	Yes	Human-readable explanation of the verdict.
`values`	No	The `values` field of the response.
`outcome`	No	The `outcome` field of the response.
`subject`	No	The `subject` field of the response.
`claim_id`	No	The `claim_id` field of the response.
`exception`	No	The `exception` field of the response.
`timestamp`	No	The `timestamp` field of the response.
`candidates`	No	The `candidates` field of the response.
`left_value`	No	The `left_value` field of the response.
`explanation`	No	The `explanation` field of the response.
`resolutions`	No	The `resolutions` field of the response.
`right_value`	No	The `right_value` field of the response.
`resolved_value`	No	The `resolved_value` field of the response.
`source_quality`	No	The `source_quality` field of the response.
`subject_filter`	No	The `subject_filter` field of the response.
`claims_examined`	No	The `claims_examined` field of the response.
`timestamp_parsed`	No	The `timestamp_parsed` field of the response.
`resolved_claim_id`	No	The `resolved_claim_id` field of the response.
`conflicts_detected`	No	The `conflicts_detected` field of the response.
`recency_breaks_ties`	No	The `recency_breaks_ties` field of the response.
`source_quality_basis`	No	The `source_quality_basis` field of the response.
`decisive_basis_present`	No	The `decisive_basis_present` field of the response.
`contradictions_examined`	No	The `contradictions_examined` field of the response.
`unresolved_disagreement`	No	The `unresolved_disagreement` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed34 schema fields changedOct 31, 2026

addedOutput schema / properties / basis

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

addedOutput schema / properties / candidates

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

addedOutput schema / properties / claim_id

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

addedOutput schema / properties / claims_examined

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

addedOutput schema / properties / conflicts_detected

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

addedOutput schema / properties / contradictions_examined

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

addedOutput schema / properties / decisive_basis_present

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

addedOutput schema / properties / detail

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

addedOutput schema / properties / exception

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

addedOutput schema / properties / explanation

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

addedOutput schema / properties / field

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

addedOutput schema / properties / left

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

addedOutput schema / properties / left_value

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

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

addedOutput schema / properties / quote

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

addedOutput schema / properties / recency_breaks_ties

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

addedOutput schema / properties / resolutions

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

addedOutput schema / properties / resolved_claim_id

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

addedOutput schema / properties / resolved_value

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

addedOutput schema / properties / right

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

addedOutput schema / properties / right_value

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

addedOutput schema / properties / source_quality

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

addedOutput schema / properties / source_quality_basis

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

removedOutput schema / properties / status

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

addedOutput schema / properties / subject

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

addedOutput schema / properties / subject_filter

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

addedOutput schema / properties / timestamp

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

addedOutput schema / properties / timestamp_parsed

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

addedOutput schema / properties / type

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

addedOutput schema / properties / unresolved_disagreement

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

addedOutput schema / properties / value

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

addedOutput schema / properties / values

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

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

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 readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower and the description still adds non-obvious context: the tool may 'preserve the disagreement' instead of forcing a resolution, and it costs $0.25 USDC. Cost disclosure is genuinely valuable behavioral information an agent would not otherwise see. The return-shape sentence is partially redundant with the output schema.

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 correctly, but the second half is grammatically broken ('use it rather than ... for conflict, not signed data snapshot') and the field-count clause is filler given an output schema exists. The intent survives, but the sentence does not earn all its space.

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?

With four params, a full-coverage schema, an output schema, and rich annotations, the description covers the essential gap — routing versus create_signed_data_snapshot and the possibility of leaving a conflict unresolved. It is complete enough to call correctly, though the garbled routing sentence slightly reduces confidence.

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 claims, prefer, subject, and recency_breaks_ties. The description adds nothing about parameter semantics beyond the schema — no mention that `prefer` governs tie-breaking or how `recency_breaks_ties` interacts with it. Baseline 3 applies.

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 clear verb+resource pair ('Resolve conflicting claims, or preserve the disagreement') and explicitly names the sibling it should not be confused with (create_signed_data_snapshot). The trailing clause about 'an object with 32 fields including basis, candidates' muddies the purpose statement by drifting into return-value territory, preventing a 5.

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 explicit routing guidance: 'use it rather than `create_signed_data_snapshot` for conflict, not signed data snapshot', which tells the agent both when to pick this tool and which alternative exists. The phrasing is garbled and no when-not-to-use condition beyond that single sibling is stated, so it falls short of 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.