Skip to main content
Glama

AceRound AI Interview Copilot

create_payment_order

Destructive

Create an order for a plan and return a Stripe Checkout link for the user to open and pay. The price is the local price for the country this request comes from and is shown in the result. After the user pays, use check_order_status to confirm. Product ids come from list_plans. Uses the user's minutes or credits or creates a payment; tell the user what it costs and get their agreement first. (Requires the user's sign-in with scope account:write.)

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": {
      "productId": "<productId>"
    },
    "name": "create_payment_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
productIdYesA product id from list_plans
deferActivationNoPasses only: true = keep the pass unactivated after payment until the user activates it (activate_subscription_card)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

The annotations only say the call is a non-read-only, destructive, non-open-world operation; the description supplies the substance behind that flag: it consumes the user's minutes or credits or creates a payment, requires sign-in with the account:write scope, and prices by the requesting country. The consent requirement makes the destructive spend explicit and actionable, which is exactly the 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.

Conciseness4/5

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

The core action and return value are front-loaded in the first sentence, with prerequisites and follow-up steps after. It is dense with useful content, though the final parenthetical auth note and the 'minutes or credits' clause make for long, comma-heavy sentences that could be split for readability.

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 only two parameters, no output schema, and a mutation that spends user credits, the definition covers the essentials: what it returns (checkout link plus displayed price), auth scope, consent, and the confirmation step. It does not mention link expiry, failure modes (unavailable plan, insufficient balance), or whether retries create duplicate orders.

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%, so both parameters, including the pass-only deferActivation behavior, are already documented in the schema. The description's only parameter-related contribution, that product ids come from list_plans, merely repeats the schema text for productId. This meets the baseline for a fully documented schema but adds no new meaning.

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?

States a specific verb and resource ('Create an order for a plan') plus the concrete output ('return a Stripe Checkout link'). It also distinguishes itself from the two closest siblings by assigning them roles: list_plans supplies product ids, check_order_status confirms payment afterward.

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?

Gives clear workflow routing: product ids come from list_plans, and post-payment confirmation goes to check_order_status. It also imposes a consent precondition ('tell the user what it costs and get their agreement first'). It stops short of stating when this tool is inappropriate (e.g., an existing pending order or an already-active subscription).

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