Skip to main content
Glama

Settle Watch

Check before paying an x402 / MPP endpoint

check_payment
Read-only

Before paying an agent-payable API (x402 or MPP), check whether it is safe: does it answer reliably, do its payment terms match its listing (no switched or burn wallets, no overcharges), and is the address it asks you to pay one the seller has proven is theirs. Returns verdict ok | caution | avoid | unknown with reasons. Pass the payTo address from the 402 response when you have it.

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": {
      "url": "<url>"
    },
    "name": "check_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe full https:// URL you are about to pay
payToNoOptional: the address its 402 response asks you to pay

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds the actual verification dimensions (reliability, switched/burn wallets, overcharges) and the full verdict vocabulary ok | caution | avoid | unknown with reasons. It does not state latency, rate limits, or that failure-to-reach yields 'unknown', which keeps it short of a 5.

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

Conciseness4/5

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

Front-loads the precondition ("Before paying...") and then enumerates the checks, with the parameter hint last. Two of the parenthetical clauses ("no switched or burn wallets, no overcharges") are dense but earn their place as concrete failure modes.

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?

For a two-parameter read-only check with no output schema, the description covers purpose, checks performed, and the returned verdict values — enough to call and interpret it. The only gap is what distinguishes 'unknown' from 'avoid' in practice.

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% and already documents both url and the optional payTo from the 402 response, so the description's instruction largely restates the schema. It adds only a weak hint that supplying payTo improves the check, which is marginal value.

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

Purpose5/5

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

States a specific verb and resource — checking an agent-payable x402/MPP endpoint before paying — and names the concrete checks (reliability, terms vs. listing, payTo provenance). An agent could not confuse this with a plain fetch or payment tool.

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

Usage Guidelines5/5

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

Explicitly says when to use it ("Before paying an agent-payable API") and gives a conditional instruction for the optional parameter ("Pass the payTo address from the 402 response when you have it"). No siblings exist, so no alternative routing is needed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.