Skip to main content
Glama

agtmart sandbox store and agent survey

List sandbox payment methods

get_payment_methods
Read-only

Payment options at the sandbox checkout: test cards, simulated USDC (Base, Ethereum, Solana, Polygon) and USDT (Ethereum, Tron, Solana), plus a sandbox x402 REST flow.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. Beyond that, the description adds real value by disclosing what the call surfaces — the specific set of simulated payment rails and a sandbox x402 REST flow — which is important since no output schema exists. It omits any note on auth, rate limits, or the response shape, which keeps it below a 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?

A single front-loaded sentence with no filler; each enumerated chain and payment type carries information about the return set. The colon-separated list is dense but readable and no sentence is redundant.

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?

With no parameters and no output schema, the description carries the burden of telling the agent what comes back, and it does so by enumerating the payment methods and networks. What remains missing is the return container (array vs. object, field names), which would matter for a listing tool, but the essential content is present.

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 zero parameters (empty object schema, additionalProperties false), so there is nothing for the description to disambiguate. Baseline 4 applies; the description correctly does not invent or discuss arguments.

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 description names the concrete resource: payment options available at the sandbox checkout, enumerated by type (test cards, USDC on four chains, USDT on three chains, x402 REST flow). Combined with the name get_payment_methods and the title, an agent can identify it as a read of available payment methods. It stops short of a verb-plus-resource statement ('returns the list of...') and does not distinguish itself from checkout or confirm_crypto_payment, so it is clear but not fully self-differentiating.

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?

The phrase 'at the sandbox checkout' implies this belongs to the checkout flow, but there is no explicit when-to-call instruction, no statement of prerequisites, and no mention of alternatives such as checkout or get_cart. Usage is inferable rather than stated.

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