Skip to main content
Glama

Checkout World

checkout_world
Destructive

Create a ten-minute public checkout intent for your existing city resident. It does not reserve the one-of-one thing; the first city reservation wins. One active checkout is allowed per market buyer and listing; wait for its ten-minute expiry before creating another. If you are not yet a resident, register in the city and choose your own name before checkout or payment. Read the card's city_status.ending before paying. Once its city offer reads phase thing_ended (the end came with no accepted payment evidence), the thing is a remnant and no new purchase can start: checkout answers 409 with no payment entry and next_step Do not pay (reason thing_ended on the JSON route; through MCP, error_class conflict and reason request_conflict). In any other phase that is not open for a new checkout, it answers 409 with reason request_conflict, no payment entry and the generic next_step.

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": {
      "listing_id": "<listing_id>",
      "city_handle": "<city_handle>"
    },
    "name": "checkout_world"
  }
}

Input Schema

NameRequiredDescriptionDefault
listing_idYes
city_handleYeslowercased and trimmed, then must match ^[a-z0-9][a-z0-9-]{2,31}$

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / city_handle / description
      Added value: +"lowercased and trimmed, then must match ^[a-z0-9][a-z0-9-]{2,31}$"
    • addedInput schema / properties / listing_id / maximum
      Added value: +2147483647
    • addedInput schema / properties / listing_id / minimum
      Added value: +1
    • changedInput schema / properties / listing_id / type
      Previous value: -"number"New value: +"integer"
  2. Added

TDQS

A3.6/5.0
Behavior4/5

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

The annotations mark the tool as destructive and open-world, and the description adds important behavior the annotations do not cover: the checkout intent does not reserve the item, the first reservation wins, the intent expires after ten minutes, only one active checkout is allowed per buyer and listing, and specific 409 conflict semantics are disclosed for the ended and non-open phases. It does not explain why the tool is destructive or what side effects it has beyond creating the intent, and it mentions no authorization requirements beyond residency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

The description is a dense block of jargon-heavy sentences that mixes at least four topics: intent lifetime, exclusivity limits, residency prerequisites, and two variants of 409 error behavior. It is front-loaded, which helps, but it repeats the 409 failure behavior across multiple sentences and spells out next_step strings that belong in the error payload.

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?

Given that there is no output schema, the description covers prerequisites, the checkout limit, the item's non-reservation status, the expiry window, and failure modes well enough for an agent to call the tool correctly. It is less complete on what a successful checkout returns and on the payment path, but the core operation is documented.

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?

Only one of the two parameters, 'city_handle', has a schema description; 'listing_id' has no description, so schema coverage is 50%. The description does add context: the listing is the 'one-of-one thing', and the handle identifies the resident or market. However, it gives no guidance on 'listing_id' format or validity, and its meaning is already implied by the schema.

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 opens with a concrete verb and resource: 'Create a ten-minute public checkout intent for your existing city resident.' The ten-minute lifetime of the intent distinguishes it from sibling tools such as 'buy' and 'draft_world', but the heavy domain jargon ('city', 'one-of-one thing') makes it unclear whether the 'city' and the 'market' are the same thing. The core action is still identifiable.

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?

The description gives explicit preconditions and ordering: the user must already be a resident, must register first if not, must wait for a prior checkout to expire, and must read 'city_status.ending' before paying. It also gives a clear usage context: one active checkout per buyer and listing. The gaps are that it does not name the alternative tools (for example, 'buy' or 'draft_world') or say when a user should choose this tool over them.

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