Skip to main content
Glama

Lumen House

get_checkout_instructions

Read-onlyIdempotent

Get exact existing checkout routes, prices, terms and private recovery requirements. Informational only. No payment challenge, signature or purchase; do not provide recovery keys.

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": {
      "id": "<id>"
    },
    "name": "get_checkout_instructions"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description earns credit by adding behavior annotations do not carry: that the result is informational only, that no purchase or signature flow is triggered, and that recovery keys must not be relayed. The one gap is not clarifying what 'private recovery requirements' concretely means in the returned data.

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?

Three short sentences, contents-first, with zero filler; the safety constraints are packed efficiently at the end. Minor deduction because 'private recovery requirements' and 'do not provide recovery keys' are allusive phrasing that costs the reader a beat without resolving itself.

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?

With no output schema, the description usefully lists the categories of data returned, which offsets the missing return documentation. However, for a tool whose sole input is an opaque patterned id, leaving that id unexplained and leaving 'recovery requirements' undefined makes the definition only marginally sufficient for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single required parameter 'id' with a strict pattern, and schema description coverage is 0%, so the description must carry the meaning. It never says what the id identifies -- a checkout route, an offer, a guide item -- or where an agent would obtain a valid value. That is a real ambiguity for the only input the tool takes.

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?

The description names a specific verb ('Get') and enumerates the concrete payload: checkout routes, prices, terms and private recovery requirements. That distinguishes it reasonably well from offer/guide siblings because it explicitly frames itself as retrieving existing checkout details rather than creating or searching anything. It stops short of naming any alternative, but the resource is unambiguous.

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 enumerated contents -- call it when you need exact checkout routes, prices or terms. The second half supplies hard prohibitions (no payment challenge, signature or purchase; don't hand over recovery keys), which is useful boundary-setting but is framed as a constraint on the call, not as when-to-prefer-this-over-siblings guidance. No alternative tool is named.

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