Compass by 402rates

Compare previous and current x402 payment terms

compare_payment_terms

Read-only

Free comparison of two unsigned captures for the same resource and method. Default analysis version 1 retains Exact EVM; version 2 compares documented Exact, Upto, Batch Settlement and Auth-Capture fields, limits and lifecycle terms. Captures are caller declarations, with no authentication, fetching or payment. Unknown profiles remain non-comparable.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "baseline": "<baseline>",
      "current": "<current>"
    },
    "name": "compare_payment_terms"
  }
}

Input Schema

Name	Required	Description
`current`	Yes
`baseline`	Yes
`analysis_version`	No	1 preserves the original Exact EVM comparison. 2 compares the pinned multi-scheme EVM profiles, including amount scope, authorizers, escrow, declared deadlines and fee bounds.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 23, 2026

addedInput schema / properties / analysis_version

Added value: +{
+  "description": "1 preserves the original Exact EVM comparison. 2 compares the pinned multi-scheme EVM profiles, including amount scope, authorizers, escrow, declared deadlines and fee bounds.",
+  "enum": [
+    "1",
+    "2"
+  ],
+  "type": "string"
+}

changedInput schema / properties / baseline / properties / challenge / description

Previous value: -"Decoded unsigned x402 v1 or v2 PaymentRequired object. Exact EVM only; at most 32 offers."New value: +"Decoded unsigned PaymentRequired object, at most 32 offers. Analysis version 1 covers x402 v1/v2 Exact EVM; analysis version 2 covers the pinned x402 v2 EVM profiles."

changedInput schema / properties / current / properties / challenge / description

Previous value: -"Decoded unsigned x402 v1 or v2 PaymentRequired object. Exact EVM only; at most 32 offers."New value: +"Decoded unsigned PaymentRequired object, at most 32 offers. Analysis version 1 covers x402 v1/v2 Exact EVM; analysis version 2 covers the pinned x402 v2 EVM profiles."

AddedOct 3, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description adds useful behavioral context: captures are caller declarations, no authentication/fetching/payment occurs, and unknown profiles are non-comparable. It still omits error behavior and response characteristics, but the added context is substantial.

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

Conciseness5/5

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

The description is front-loaded with the core comparison purpose and then adds compact details about versions, capture semantics, and non-comparable profiles. Every sentence contributes relevant information without repetition.

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?

For a nested-input comparison tool with no output schema and only partial schema description coverage, the description covers the main input semantics and safety context. However, it does not describe the comparison result structure or error cases, leaving a meaningful completeness gap.

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 low at 33%, so the description must compensate. It meaningfully explains analysis_version behavior and notes that captures must be for the same resource and method, but it does not fully clarify the baseline/current capture objects beyond the schema’s nested field descriptions.

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 specific verb and resource: comparing two unsigned captures for the same resource and method. It clearly scopes the operation to payment-terms comparison and version-dependent coverage, but it does not explicitly distinguish this tool from sibling tools such as check_payment_terms.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by saying it compares two captures and gives guidance on analysis version selection. However, it does not explicitly state when to use this tool versus alternatives like check_payment_terms, nor does it provide when-not-to-use conditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Compass by 402rates tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?