Skip to main content
Glama

start_payment

Open the checkout page for a payment request (ref FA-P-XXXXXXXX). Returns checkout_url: open it for your human, or pay there with a payment method your human gave you. Nothing is charged until the payer completes that page.

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": {
      "payment_ref": "<payment_ref>"
    },
    "name": "start_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoWhere the receipt goes
agent_nameNo
payment_refYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that nothing is charged until the payer completes the page and what the return value means, but stays silent on repeat-call behavior (does calling twice create two checkout sessions?), URL expiry, and any auth or permission requirements.

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?

Three short sentences, purpose first, then result handling, then the key safety fact about when money moves. No filler and nothing buried.

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?

For a payment-initiation tool with no annotations and no output schema, the description covers purpose, return value, and the critical no-charge-until-completion behavior. The remaining gaps are the undocumented agent_name parameter and the absence of any guidance on idempotency or invalid refs.

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 only 33%, so the description must compensate. It does explain payment_ref's expected format, and the schema covers email ("Where the receipt goes"), but agent_name is undocumented in both places, leaving real ambiguity about what identity is recorded or how it is used.

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?

"Open the checkout page for a payment request" is a specific verb plus resource, and the ref format (FA-P-XXXXXXXX) makes the target concrete. It implicitly distinguishes itself from get_payment, which presumably reads payment state rather than opening a checkout, though no sibling is named 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 description tells the agent exactly what to do with the result: open checkout_url for the human, or pay there with a payment method the human already supplied. It gives clear operating context but no exclusions, prerequisites, or alternatives for cases where a checkout shouldn't be opened.

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