Skip to main content
Glama

Test MPP payment

payment_check

Optional wallet self-test: makes one MPP payment and returns its receipt, proving your client can pay end to end. No other tool needs a payment, so skip it unless you are testing a wallet. Each call is charged and changes nothing else on ClawdMarket. Costs $0.001 per call (pathUSD via MPP).

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": "payment_check"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that each call is charged, costs $0.001, returns a receipt, and changes nothing else on ClawdMarket. This is consistent with the non-read-only, non-idempotent, non-destructive annotations and usefully clarifies the charged side effect.

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 short and front-loaded with the core purpose, then gives usage guidance, side-effect scope, and cost. Every sentence adds useful information without unnecessary detail.

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?

Given that there are no parameters and no output schema, the description supplies everything an agent needs: what the tool does, when to use it, what it returns, what it costs, and what it changes. The annotations cover safety hints, and the description fills in the charged-payment context.

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 has zero parameters, so the baseline is 4. The description does not need to explain parameter semantics, and it appropriately focuses on behavior and cost instead.

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?

The description states a specific verb and resource: it makes one MPP payment and returns its receipt as a wallet self-test. It also distinguishes the tool from siblings by saying no other tool needs a payment, so an agent can identify this as an isolated payment-testing utility.

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?

The description gives explicit when-to-use guidance: use it only when testing a wallet, and skip it otherwise because no other tool requires payment. It also makes clear this is optional, which prevents unnecessary charged calls.

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