Skip to main content
Glama

AIFEC

checkout_payment_options

Read-only

The payment methods offered for the order, with their kind (offline: transfer or cash on delivery; redirect: paid online) and any fee, and the one selected.

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

Input Schema

NameRequiredDescriptionDefault
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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile needs no restating. Beyond that, the description usefully discloses what comes back — method kinds (offline: transfer or cash on delivery; redirect: paid online), any fee, and which one is selected — which matters because no output schema exists. It still omits what happens when no options are available or how errors surface.

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?

One compact sentence with no filler, and the primary content (the payment methods) leads. The phrasing 'and the one selected' is slightly clipped and grammatically loose, but nothing is wasted.

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 read-only getter with no output schema, the description covers the return payload in enough detail (kinds, fee, selection) that an agent knows what it will receive. Only edge-case behavior — empty option lists, whether the order must exist first — is missing.

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?

The single session_id parameter has 100% schema description coverage, including when to supply it and its cart-persistence effect, so the schema carries the semantics. The description adds nothing about parameters, which is acceptable at full coverage but is the baseline, not more.

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?

Names a specific resource (the payment methods offered for the order) and enumerates what it contains, including the currently selected one, which separates it from the mutating sibling checkout_set_payment. The only weakness is that no explicit verb (returns/lists) is stated, so the retrieval nature is inferred rather than declared.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use statement, no mention of a prerequisite (e.g. an already-created order), and no named alternative such as checkout_set_payment or checkout_status. The implied workflow of checking options before selecting one is left entirely to the agent.

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