Skip to main content
Glama

Little Works

create_checkout

Stripe checkout entry (recipe buy, verification). Authenticated users complete in browser.

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

Input Schema

NameRequiredDescriptionDefault
kindYesrecipe|verification|storage
slugNo
apiKeyNoRequired when LITTLEWORKS_MCP_API_KEY is set on the server

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does usefully disclose that this is a Stripe flow completed in the browser and that authentication is required, but it says nothing about what the call returns (checkout URL vs session id), whether a charge occurs, whether calling twice creates duplicate sessions, or what the apiKey gates. For a payment-adjacent tool, that leaves major gaps.

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

Conciseness3/5

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

Two short phrases with no filler, but they are telegraphic fragments rather than complete statements, and "entry" is doing ambiguous work. Front-loading is fine; the problem is under-specification rather than verbosity.

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?

For a 3-parameter tool with an enum-like kind, no annotations, and no output schema, the description should at minimum explain the return value and the payment semantics. It covers the browser-redirect and auth aspects but leaves the return contract and the "storage" kind unexplained.

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 67%, and the schema already documents both the kind values (recipe|verification|storage) and the apiKey condition. The description mentions only two of the three kinds, omitting "storage", and never explains what slug refers to. It adds marginal meaning over the schema and is slightly incomplete relative to it.

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

Purpose3/5

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

"Stripe checkout entry" identifies the resource (a Stripe checkout) but the verb is only implied by the tool name and "entry" is vague about whether this creates a session, returns a URL, or opens a flow. Two of the three kinds are named ("recipe buy, verification"), so an agent gets partial scope. It is distinguishable from siblings like buy_recipe, but the core action stays ambiguous.

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?

The description supplies no explicit when-to-use or when-not-to-use guidance and never names an alternative such as buy_recipe or buy_project. "Authenticated users complete in browser" is a precondition for the human, not a selection rule for the agent. The agent must infer routing from the tool name alone.

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