Skip to main content
Glama

AIFEC

checkout_set_payment

Read-only

Choose the payment method (method = the id from checkout_payment_options).

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

Input Schema

NameRequiredDescriptionDefault
methodYes
session_idNoOnly if your client does not keep the MCP session (the Mcp-Session-Id header): the session_id that an earlier answer of this server gave you. It keeps the same cart between calls.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotation readOnlyHint=true supplies the safety profile, and the schema's session_id text adds the useful context that cart state persists across calls. The description itself adds almost nothing behavioral: it does not say whether this mutates stored checkout state, whether it needs a non-empty cart, or that it does not finalize the order (checkout_place does).

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?

One sentence, front-loaded with the action, with the parameter hint attached inline. Nothing superfluous and nothing buried.

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

Completeness3/5

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

For a one-parameter setter with readOnlyHint annotations and no output schema, this is minimally sufficient to invoke. It falls short on prerequisite state (cart in progress) and flow ordering, which matter for a checkout step whose sibling checkout_place completes the order.

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?

Schema coverage is 50%, and the description compensates for the undocumented required 'method' by explaining it is an id drawn from checkout_payment_options — the single most important semantic an agent needs. session_id is already described in the schema, so the remaining gap is minor (no format or length hints for method).

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?

"Choose the payment method" is a specific verb+resource, and the parenthetical points to checkout_payment_options as the source of valid ids. It distinguishes the tool from sibling setters like checkout_set_customer and from the terminal checkout_place, though it never names them explicitly.

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 only implied: an agent can infer it must call checkout_payment_options first, then this tool. There is no statement of where this sits in the checkout sequence (before checkout_place), whether an existing cart is required, or whether calling it twice is allowed.

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