Skip to main content
Glama

Lokand Restaurant MCP

Create checkout link

create_checkout_link

Create a Stripe Checkout link to upgrade a business to a paid plan. Hand the returned URL to the customer — anyone who opens it can pay; the plan activates automatically after payment (3-month free trial). Pass customer_country (ISO 3166-1 alpha-2) so first-time pricing is quoted in the customer's region, not the agent's.

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": {
      "business_id": "<business_id>",
      "product_key": "<product_key>"
    },
    "name": "create_checkout_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
business_idYes
product_keyYesThe plan to purchase (Pro is monthly-only)
customer_countryNoCustomer's ISO country code, e.g. DE

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Adds substantial behavior beyond the annotations: the returned URL is a bearer-style artifact ('anyone who opens it can pay'), activation is automatic post-payment, and there is a 3-month free trial. It complements openWorldHint/idempotentHint=false without contradicting them. It stops short of stating auth requirements, whether the paid plan is immediate or deferred, or what happens on repeat calls, which is why it is not a 5.

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 sentences, front-loaded with what is created, then what to do with the result, then the parameter caveat. Every sentence carries distinct information with no restatement of the schema.

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, the description correctly covers the return value ('the returned URL') and the post-call flow. Missing only edge behavior such as repeated link creation for an already-subscribed business or failure modes, which an agent handling billing would benefit from.

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?

At 67% schema coverage the description meaningfully supplements the schema: it explains WHY customer_country matters (first-time pricing is quoted in the customer's region) and warns against defaulting to the agent's own region, which the schema's 'e.g. DE' does not convey. business_id remains undescribed in both places, so it is not complete.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Create a Stripe Checkout link') plus the concrete goal ('upgrade a business to a paid plan'). This is unmistakably a payment-link generator and cannot be confused with any sibling such as get_billing_summary or apply_country_settings.

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?

Makes the use case explicit: upgrade a business to a paid plan, then hand the URL to the customer. It does not name an alternative tool or state when NOT to call it (e.g. business already on a paid plan), but no sibling in the list performs a comparable action, so the guidance is sufficient in practice.

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