Skip to main content
Glama

Little Works

buy_recipe

Recipe purchase checkout entry when priced.

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": {
      "slug": "<slug>"
    },
    "name": "buy_recipe"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes
apiKeyNoRequired when LITTLEWORKS_MCP_API_KEY is set on the server

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.9/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full behavioral burden for what is clearly a purchase/mutation tool, and it discloses nothing. There is no statement about whether money is charged, whether the call is idempotent, what permissions or API key are needed, what happens when the recipe is unpriced, or what the response contains.

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?

A single short sentence, front-loaded with the verb, with no filler. It is efficient but achieved by under-specification rather than by careful compression, so brevity costs information here.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a transactional tool with no annotations and no output schema, an agent needs to know cost/side effects and the result of the call; the description provides neither. The "when priced" qualifier is the only behavioral constraint offered, leaving the definition incomplete for a purchase action.

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 only 50%: slug has no description in the schema and the tool description adds no meaning for it (format, whether it is a recipe id or handle). The apiKey parameter is documented in the schema, not the description, so the description compensates for none of the coverage gap.

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

Purpose2/5

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

"Recipe purchase checkout entry when priced" mostly restates the name buy_recipe, swapping the verb for a synonym and appending "checkout entry". The only added detail is that it applies to priced recipes, but the tool's actual effect (does it complete a purchase, create a checkout session, or just open an entry point?) is left ambiguous against siblings like create_checkout and buy_material.

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?

"When priced" implies a precondition (the recipe must have a price), which is a hint of when to use it, but there is no explicit when/when-not guidance and no mention of the alternative path for unpriced recipes or how this differs from create_checkout. An agent must guess whether this charges money or merely prepares a checkout.

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