Skip to main content
Glama

Airsockfly

Start payment

start_payment
Idempotent

Start payment for an order and get a secure Stripe checkout URL. The user must open the URL and pay personally. The agent never pays and must not claim that a payment was made.

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

Input Schema

NameRequiredDescriptionDefault
methodYesPayment method the user will use on the payment page.
orderIdYesOrder identifier from list_bookings or create_booking.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, idempotentHint=true, destructiveHint=false; the description adds the crucial behavioral fact that the call produces an external Stripe checkout URL the user must open themselves, and that the agent must never pay or claim a payment occurred. This pre-empts the most likely agent failure mode and is exactly the kind of context annotations cannot convey.

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, front-loaded with purpose and return value, then the agent-conduct constraint. No redundant restatement of the title or schema.

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 two-parameter tool with no output schema, the description covers what is produced (a checkout URL) and the key conduct rule. It leaves unstated what happens if a session already exists (the idempotentHint suggests reuse) and how the agent should confirm completion, which is left to get_payment_status.

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 description coverage is 100%, with both orderId (24-hex, sourced from list_bookings or create_booking) and the method enum documented in the schema. The description adds no meaning beyond that, so the baseline of 3 applies.

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?

States a specific verb and resource ("Start payment for an order") plus the concrete outcome ("get a secure Stripe checkout URL"). That is enough to separate it from read-only siblings like get_payment_status, though the description never names the sibling it displaces.

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 constraint that the user must personally open the URL and pay, which tells the agent this is the hand-off step. It gives no explicit when-to-use rule relative to alternatives (e.g., checking get_payment_status before starting, or whether an existing unpaid order already has a session).

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