Skip to main content
Glama

Black Label Real Estate Website MCP

create_checkout

Start a purchase of one offer. Returns a continue_url: send the buyer there to pay on the Stripe-hosted checkout page. This tool does not charge anything.

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": {
      "offer_id": "<offer_id>"
    },
    "name": "create_checkout"
  }
}

Input Schema

NameRequiredDescriptionDefault
offer_idYes
quantityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false), the description adds the crucial fact that no charge occurs and that payment happens off-tool on a Stripe-hosted page, which explains the openWorldHint. It does not mention session expiry, idempotency behavior, or failure modes for a non-idempotent mutation.

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?

Three short sentences with the action, the return value, and the key safety caveat front-loaded in that order. No filler or redundant restatement of the tool name.

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 no output schema and only two parameters, the description covers the essential contract: create a session, hand back continue_url, no charge is made. Missing details such as quantity semantics, session lifetime, and error conditions keep it from being fully complete.

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?

Schema coverage is 0%, so the description carries the burden, yet it only implies that one offer is purchased and says nothing about offer_id's meaning or the quantity parameter (capped at 1). The enum values are self-explanatory in the schema, but the description adds almost no semantic depth.

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?

"Start a purchase of one offer" names a specific verb and resource, and the following sentence clarifies that this only creates a session rather than performing the purchase. It does not explicitly differentiate itself from the sibling get_checkout, so an agent must infer the split between creating and retrieving a checkout.

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 "send the buyer there to pay on the Stripe-hosted checkout page," which tells the agent what to do with the result. There is no explicit when-to-use versus get_checkout/list_products guidance and no statement of preconditions or exclusions.

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