Skip to main content
Glama

Nalvorn Checks

payment_verdict

Read-only

Verdict on a Base payment: paid, underpaid, wrong recipient, pending or reverted, with chain facts and a signed receipt Costs 0.01 USDC per call on Base (x402). Call it over HTTP with a PAYMENT-SIGNATURE header to actually run 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": {
      "tx": "<tx>"
    },
    "name": "payment_verdict"
  }
}

Input Schema

NameRequiredDescriptionDefault
txYestx
tokenNotoken
expect_toNoexpect_to
expect_amountNoexpect_amount
min_confirmationsNomin_confirmations

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses the two facts an agent most needs and could not otherwise know: a 0.01 USDC per-call cost via x402 and the requirement to send a PAYMENT-SIGNATURE header over HTTP for the call to actually execute. It also hints at the return payload (chain facts plus a signed receipt). It does not say what happens when the header or payment is absent, which is the remaining behavioral gap.

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?

Two sentences, purpose front-loaded, with cost and transport requirement following. Mildly sloppy: a missing period between "signed receipt" and "Costs 0.01 USDC" makes the pricing clause read as a run-on, and "Call it over HTTP" could be tighter.

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 no output schema, the description carries return-value burden and only sketches it ("chain facts and a signed receipt") without saying what the verdict object looks like. Combined with the vacuous parameter descriptions and no failure-mode guidance, it is adequate to start a call but not to model the result or handle payment rejection.

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 formal baseline is 3, but the coverage is cosmetic — every schema description merely repeats the parameter name ("tx": "tx"), so the schema conveys no real semantics. The description does not compensate at all: it never clarifies that tx is the transaction hash, that expect_to/expect_amount are assertions that drive the "wrong recipient"/"underpaid" verdicts, or what min_confirmations changes. A 3 reflects the baseline rather than genuine added value.

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?

States a specific verb+resource ("Verdict on a Base payment") and enumerates the outcome space (paid, underpaid, wrong recipient, pending, reverted), which tells an agent exactly what class of question this answers. It stops short of naming or contrasting any sibling (e.g. receipt_verify), so differentiation is left to the outcome list alone.

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?

Usage is only implied: an agent can infer this is for adjudicating whether a Base payment settled correctly, but there is no explicit statement of when to prefer it over alternatives such as receipt_verify. The second sentence gives invocation mechanics (HTTP + PAYMENT-SIGNATURE header), which is how-to-call guidance rather than when-to-use guidance.

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