Synthex Forge — x402 Paid Agent Services

Check Operation Idempotency

check_operation_idempotency

Read-onlyIdempotent

Compare a request about. use it rather than assess_operation_behaviour_drift for operation idempotency, not operation behaviour drift; an object with 33 fields including action, canonical_request. $0.01 USDC.

Input Schema

Name	Required	Description
`history`	No	The history this operation operates on. See the schema for its type and whether it is required.
`request`	No	The request this operation operates on. See the schema for its type and whether it is required.
`ignore_fields`	No	The ignore fields this operation operates on. See the schema for its type and whether it is required.
`near_duplicate_threshold`	No	The near duplicate threshold 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.
`entry`	No	The `entry` field of the response.
`field`	No	The `field` field of the response.
`action`	No	The `action` field of the response.
`detail`	Yes	Human-readable explanation of the verdict.
`reason`	No	Why the verdict was reached.
`problems`	No	The `problems` field of the response.
`exception`	No	The `exception` field of the response.
`operation`	No	The `operation` field of the response.
`principal`	No	The `principal` field of the response.
`near_match`	No	The `near_match` field of the response.
`similarity`	No	The `similarity` field of the response.
`differences`	No	The `differences` field of the response.
`exact_match`	No	The `exact_match` field of the response.
`fingerprint`	No	The `fingerprint` field of the response.
`recorded_at`	No	The `recorded_at` field of the response.
`entry_sha256`	No	The `entry_sha256` field of the response.
`this_request`	No	The `this_request` field of the response.
`history_entry`	No	The `history_entry` field of the response.
`matched_entry`	No	The `matched_entry` field of the response.
`ignored_fields`	No	The `ignored_fields` field of the response.
`request_sha256`	No	The `request_sha256` field of the response.
`idempotency_key`	No	The `idempotency_key` field of the response.
`near_duplicates`	No	The `near_duplicates` field of the response.
`verdict_meaning`	No	The `verdict_meaning` field of the response.
`canonical_request`	No	The `canonical_request` field of the response.
`history_available`	No	The `history_available` field of the response.
`history_entry_sha256`	No	The `history_entry_sha256` field of the response.
`idempotency_key_sha256`	No	The `idempotency_key_sha256` field of the response.
`operation_scope_sha256`	No	The `operation_scope_sha256` field of the response.
`idempotency_key_present`	No	The `idempotency_key_present` field of the response.
`near_duplicate_threshold`	No	The `near_duplicate_threshold` field of the response.
`history_entries_considered`	No	The `history_entries_considered` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed35 schema fields changedOct 31, 2026

addedOutput schema / properties / action

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

addedOutput schema / properties / canonical_request

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

addedOutput schema / properties / detail

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

addedOutput schema / properties / differences

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

addedOutput schema / properties / entry

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

addedOutput schema / properties / entry_sha256

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

addedOutput schema / properties / exact_match

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

addedOutput schema / properties / exception

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

addedOutput schema / properties / field

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

addedOutput schema / properties / fingerprint

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

addedOutput schema / properties / history_available

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

addedOutput schema / properties / history_entries_considered

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

addedOutput schema / properties / history_entry

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

addedOutput schema / properties / history_entry_sha256

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

addedOutput schema / properties / idempotency_key

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

addedOutput schema / properties / idempotency_key_present

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

addedOutput schema / properties / idempotency_key_sha256

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

addedOutput schema / properties / ignored_fields

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

addedOutput schema / properties / matched_entry

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

addedOutput schema / properties / near_duplicate_threshold

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

addedOutput schema / properties / near_duplicates

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

addedOutput schema / properties / near_match

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

addedOutput schema / properties / operation

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

addedOutput schema / properties / operation_scope_sha256

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

addedOutput schema / properties / principal

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

addedOutput schema / properties / problems

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

addedOutput schema / properties / reason

Added value: +{
+  "description": "Why the verdict was reached.",
+  "type": "string"
+}

addedOutput schema / properties / recorded_at

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

addedOutput schema / properties / request_sha256

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

addedOutput schema / properties / similarity

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

removedOutput schema / properties / status

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

addedOutput schema / properties / this_request

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

addedOutput schema / properties / type

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

addedOutput schema / properties / verdict_meaning

Added value: +{
+  "description": "The `verdict_meaning` 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 readOnly=true, idempotent=true, destructive=false, openWorld=false, so the safety profile is covered. The description adds genuinely new context — a $0.01 USDC cost and the shape of the compared object (33 fields including action, canonical_request) — but says nothing about what a comparison verdict looks like or how thresholds affect the result.

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?

It is short, but it is not clean: the opening clause is a broken fragment ("Compare a request about.") and the pricing note trails awkwardly after the schema hint. Brevity here comes from truncation rather than disciplined editing.

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?

For a comparison tool with four parameters, a nested request object, and a similarity threshold, the description leaves the core mechanic unexplained — what constitutes an idempotency match, how near_duplicate_threshold or ignore_fields alter the verdict. An output schema exists so return values needn't be spelled out, but the input-side semantics gap is substantial.

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 the baseline is 3, though the schema's own descriptions are boilerplate ("the request this operation operates on"). The description adds only a partial hint that the request object carries 33 fields including action and canonical_request; it never mentions history, ignore_fields, or near_duplicate_threshold, which are the parameters that actually determine behavior.

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 verb "Compare" plus the sibling contrast ("for operation idempotency, not operation behaviour drift") tells an agent roughly what domain this tool covers. But the object of the sentence is truncated ("Compare a request about."), so the tool's actual output/purpose is only inferable from the name and title rather than stated.

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 it should be preferred over: "use it rather than `assess_operation_behaviour_drift` for operation idempotency, not operation behaviour drift." That is a concrete routing rule against a real sibling. It stops short of stating prerequisites or when-not-to-use conditions beyond that one contrast.

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.