Open Solid

Make a payment

pay

Destructive

PAID. Make a payment from the wallet: type is usa_card, gift_card, venmo, paypal, bank, debit, or x402 (call any x402-priced API: give url, max_usd and optionally method and body; returns the API's response). Enforces the spend limit on the fee-inclusive total. Always include a one-sentence note.

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": {
      "type": "<type>",
      "note": "<note>"
    },
    "name": "pay"
  }
}

Input Schema

Name	Required	Description	Default
`url`	No
`body`	No
`note`	Yes
`type`	Yes
`amount`	No
`method`	No
`country`	No
`max_usd`	No
`currency`	No
`last_name`	No
`first_name`	No
`recipient_id`	No
`destination_id`	No
`laso_server_id`	No
`idempotency_key`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 24, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=false, so the safety profile is known. The description adds value by disclosing that spend limits are enforced on the fee-inclusive total, that a one-sentence note is required, and that x402 payments return the API's response.

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

Conciseness3/5

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

The description is a single rambling paragraph that starts with an unnecessary 'PAID.' and packs multiple clauses without clear separation. It is adequately concise but not front-loaded or well-structured for quick parsing.

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

Completeness2/5

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

For a 15-parameter destructive, open-world mutation tool with no output schema, the description is incomplete. It does not explain return values for non-x402 payments, does not cover most parameter semantics, and omits key behavioral details such as idempotency key usage or failure modes.

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

Parameters2/5

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

With 15 parameters and 0% schema description coverage, the description only explains the 'type' parameter (listing valid values) and the x402-specific parameters (url, max_usd, method, body). It leaves most other parameters (e.g., amount, currency, first_name, last_name, recipient_id, idempotency_key) undocumented, failing to compensate for the schema gap.

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 ('Make a payment') and resource ('from the wallet'), and enumerates the supported payment types. It clearly distinguishes this tool from the read-only siblings without needing to name them.

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 implied by the action and the note that a one-sentence note is always required. For the x402 type, it specifies to give url, max_usd, and optionally method and body, but it does not explicitly state when to use this tool versus alternatives (which are all read-only, so the need is minimal).

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

All Open Solid tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?