Synthex Forge — x402 Paid Agent Services

Build Dispute Counterparty Record

build_dispute_counterparty_record

Destructive

What is shown to a counterparty is the record. use it rather than assess_dispute_evidence for dispute counterparty record, not dispute evidence; an object with 53 fields including agent_id, amount_field. $1.15 USDC.

Input Schema

Name	Required	Description
`record.record`	No	[POST /v1/commerce/dispute-evidence]
`record.dispute_id`	No	[POST /v1/commerce/dispute-evidence]
`commitments.agent_id`	No	[POST /v1/autonomy/commitment-check]
`commitments.commitments`	No	[POST /v1/autonomy/commitment-check]
`commitments.observations`	No	[POST /v1/autonomy/commitment-check]

Output Schema

Name	Required	Description
`at`	No	The `at` field of the folded answer.
`id`	No	The `id` field of the folded answer.
`ok`	No	Whether every inner call succeeded.
`due`	No	The `due` field of the folded answer.
`raw`	No	The `raw` field of the folded answer.
`kind`	No	The `kind` field of the folded answer.
`note`	No	The `note` field of the folded answer.
`text`	No	The `text` field of the folded answer.
`type`	No	The `type` field of the folded answer.
`count`	No	The `count` field of the folded answer.
`state`	No	The `state` field of the folded answer.
`detail`	No	The `detail` field of the folded answer.
`reason`	No	The `reason` field of the folded answer.
`states`	No	The `states` field of the folded answer.
`status`	No	The `status` field of the folded answer.
`outcome`	No	The `outcome` field of the folded answer.
`results`	No	One result per inner call.
`section`	No	The `section` field of the folded answer.
`summary`	No	One-line summary of the folded answer.
`agent_id`	No	The `agent_id` field of the folded answer.
`evidence`	No	The `evidence` field of the folded answer.
`sections`	No	The `sections` field of the folded answer.
`exception`	No	The `exception` field of the folded answer.
`reference`	No	The `reference` field of the folded answer.
`attempt_id`	No	The `attempt_id` field of the folded answer.
`dispute_id`	No	The `dispute_id` field of the folded answer.
`commitments`	No	The `commitments` field of the folded answer.
`event_count`	No	The `event_count` field of the folded answer.
`amount_field`	No	The `amount_field` field of the folded answer.
`match_method`	No	The `match_method` field of the folded answer.
`observations`	No	The `observations` field of the folded answer.
`state_counts`	No	The `state_counts` field of the folded answer.
`commitment_id`	No	The `commitment_id` field of the folded answer.
`contradiction`	No	The `contradiction` field of the folded answer.
`core_complete`	No	The `core_complete` field of the folded answer.
`kept_fraction`	No	The `kept_fraction` field of the folded answer.
`payee_present`	No	The `payee_present` field of the folded answer.
`payer_present`	No	The `payer_present` field of the folded answer.
`section_order`	No	The `section_order` field of the folded answer.
`artefact_count`	No	The `artefact_count` field of the folded answer.
`contradictions`	No	The `contradictions` field of the folded answer.
`currency_field`	No	The `currency_field` field of the folded answer.
`observation_id`	No	The `observation_id` field of the folded answer.
`commitment_text`	No	The `commitment_text` field of the folded answer.
`reference_field`	No	The `reference_field` field of the folded answer.
`commitment_count`	No	The `commitment_count` field of the folded answer.
`observation_text`	No	The `observation_text` field of the folded answer.
`present_fraction`	No	The `present_fraction` field of the folded answer.
`observation_count`	No	The `observation_count` field of the folded answer.
`checkable_fraction`	No	The `checkable_fraction` field of the folded answer.
`observation_outcome`	No	The `observation_outcome` field of the folded answer.
`self_reported_status`	No	The `self_reported_status` field of the folded answer.
`artefacts_with_verifiable_content`	No	The `artefacts_with_verifiable_content` field of the folded answer.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and non-read-only, so the safety profile is covered. The description adds useful non-schema context — that the record is externally visible to a counterparty, that it contains 53 fields, and that it costs $1.15 USDC — but says nothing about what 'destructive' means here or what happens to prior records.

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?

It is short but structured as one awkward run-on with a dangling opening ('What is shown to a counterparty is the record'), and the most actionable routing clause is buried mid-sentence. Every element earns its place, but the ordering and grammar undercut readability.

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?

With annotations and an output schema present, most burden is lifted, and the description adds pricing, field count, and sibling routing. However, for a destructive, externally-visible write tool, it omits what gets overwritten or the significance of the counterparty-facing record, leaving gaps.

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 coverage is 100%, so parameters are documented in the schema. The description adds a little meaning by noting the record is an object with 53 fields including agent_id and amount_field, but this is marginal against a fully documented nested schema. Baseline 3 is appropriate.

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 description implies the tool builds a record of what a counterparty sees and mentions 'dispute counterparty record', but the phrasing is fragmented ('What is shown to a counterparty is the record') rather than a clean verb+resource statement. The distinguishing clause against `assess_dispute_evidence` helps, but an agent must lean on the name/title to infer the actual action.

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 (`assess_dispute_evidence`) and states the selecting condition ('for dispute counterparty record, not dispute evidence'), which is a clear routing rule. It stops short of broader when/when-not context, but the core alternative is spelled out.

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.