Skip to main content
Glama

SCRIPTMASTERLABS — Provider Trust + CANON

Check Payment

check_payment
Read-onlyIdempotent

Check live x402 payment readiness and real settlement evidence: the canonical x402 payment contract, the readiness endpoint, and recorded settlement evidence, returned as separate envelopes. A 402 challenge, a signature, a readiness flag, or an HTTP 200 alone does not prove settled, accepted delivery — only settlement evidence does. Free, read-only; never signs or spends.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, and the description reinforces these ('Free, read-only; never signs or spends'). More valuably, it discloses a behavioral guarantee the annotations cannot: only settlement evidence proves delivery, and the three result sets are returned as separate envelopes rather than a single merged verdict.

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?

Two sentences, purpose first, caveat second, with no filler. The colon-delimited list of returned artifacts conveys the shape of the output without wasted words.

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?

There is no output schema, so the description carries the return-value burden and does so by naming the three envelopes. Residual gaps are minor for a zero-parameter read-only check: it does not say how to interpret the readiness flag or what an empty evidence envelope means.

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?

The tool takes no parameters, so the baseline of 4 applies. Nothing in the description conflicts with the empty schema, and no additional parameter meaning is needed.

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 definition names a specific verb and resource (check live x402 payment readiness) and enumerates exactly what the tool returns: the canonical payment contract, the readiness endpoint, and recorded settlement evidence, each in its own envelope. An agent can distinguish it from check_status or check_identity by the payment-settlement focus, though it never names those siblings explicitly.

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?

The second sentence effectively defines the use case: use this when you need proof of settled, accepted delivery rather than an ambiguous 402 challenge, signature, readiness flag, or HTTP 200. It gives clear context but no explicit statement of when not to use it or which sibling to pick instead.

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