Skip to main content
Glama

Check payment

check_payment
Read-only

CALL THIS BEFORE PAYING ANY SELLER, so your task doesn't fail on a dead, mislisted or flagged one. Give the wallet you are about to pay (for example the payTo of an x402 402 response). Returns verdict ok, careful or stop, one sentence of advice, the next step, and when the verdict isn't ok, other sellers of the same service to use instead. The evidence behind it: payments the wallet received, buyers who came back, delivery reports, and whether its listed services answer. If the verdict is stop, do not pay. Free, no key.

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

Input Schema

NameRequiredDescriptionDefault
detailNoOptional: true for the full evidence (payments, buyers, services, prices). Left out, the answer is short: verdict, advice, next step, sellers to pay instead when there are, and the signed verdict.
pay_toYesThe wallet address you are about to pay (the payTo): a 0x address, or a Solana one.
resourceNoOptional: the URL you are paying for (the resource in the x402 payment request). Lets the answer name other sellers of that same service if this one isn't ok.
amount_usdNoOptional: how much you're about to pay, in US dollars. Big payments need a stronger record to get ok.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / detail
      Added value: +{
      +  "description": "Optional: true for the full evidence (payments, buyers, services, prices). Left out, the answer is short: verdict, advice, next step, sellers to pay instead when there are, and the signed verdict.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / resource
      Added value: +{
      +  "description": "Optional: the URL you are paying for (the resource in the x402 payment request). Lets the answer name other sellers of that same service if this one isn't ok.",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / pay_to / description
      Previous value: -"The 0x wallet address you are about to pay (the payTo)."New value: +"The wallet address you are about to pay (the payTo): a 0x address, or a Solana one."
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Goes well beyond the annotations (readOnly, non-destructive) by disclosing the return contract (verdict tiers, one-line advice, next step, alternative sellers), the evidence sources used (payments received, returning buyers, delivery reports, service liveness), and cost/auth facts ('Free, no key'). Lacks detail on failure modes or latency, so not a full 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?

The imperative trigger is front-loaded in the first clause, followed by return shape and evidence. Dense but nearly all sentences carry actionable information; the promotional tone ('so your task doesn't fail') adds slight redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only lookup with no output schema, the description fully covers inputs, the shape of the answer, the decision rule on the verdict, and cost. Nothing needed to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description adds workflow meaning by framing pay_to as the x402 payTo from a 402 response you're about to pay, and explains why resource/amount matter (naming other sellers, stronger record needed for big payments). This exceeds what the schema alone conveys.

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 ('check' the wallet you're about to pay) and immediately frames the precondition ('CALL THIS BEFORE PAYING ANY SELLER'), plus the return shape (verdict ok/careful/stop). An agent can distinguish it from check_trust or find_seller without opening any schema.

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?

Gives explicit trigger conditions: call before paying any seller, pass the wallet you're about to pay, and act on the verdict ('If the verdict is stop, do not pay'). It doesn't explicitly contrast with siblings like check_trust, which keeps it from a 5.

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.

Resources