Skip to main content
Glama

Little Works

start_recipe

Start a recipe. Pass projectId/slug + brief to run the shared Project→Recipe+BOM+booking package writer (same as in-app AI Project Manager). Otherwise returns the cook landing stub.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "start_recipe"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo
slugNo
briefNo
apiKeyNoRequired when LITTLEWORKS_MCP_API_KEY is set on the server
projectIdNo
bookingUrlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / apiKey
      Added value: +{
      +  "description": "Required when LITTLEWORKS_MCP_API_KEY is set on the server",
      +  "type": "string"
      +}
    • addedInput schema / properties / bookingUrl
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / brief
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / city
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / projectId
      Added value: +{
      +  "type": "string"
      +}
  2. First observed

TDQS

C2.8/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden; it does disclose that this is a multi-entity write (project, recipe, BOM, booking) and that a degraded fallback path exists, which is useful. It omits permissions/auth requirements beyond the apiKey mention, idempotency, side effects on existing projects, and what distinguishes the two return modes.

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

Conciseness4/5

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

Two compact sentences that front-load the action and then the fallback case; nothing is padded. The only weakness is that the second sentence packs multiple concepts into one clause chain, slightly reducing readability.

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 six-parameter, side-effect-heavy write tool with no annotations and no output schema, the description is too thin: it does not explain required parameter combinations, what the returned package contains, or the failure modes. An agent would be guessing about what to pass and what it gets back.

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?

Schema coverage is only 17%, so the schema does little work, yet the description adds meaning for three of six parameters: projectId/slug (alternatives), and brief (drives the package writer). city, bookingUrl, and the interaction between projectId and slug when both or neither are supplied remain unexplained.

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?

The lead sentence "Start a recipe" largely restates the tool name, while the second sentence adds real specificity by naming the shared Project→Recipe+BOM+booking package writer and the in-app analogue. However, domain terms like "recipe" and "cook landing stub" are never defined, so an agent cannot fully picture what the tool produces.

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 gives a conditional (pass projectId/slug + brief → run the writer; otherwise → stub) but no when-to-use guidance relative to siblings such as start_project, buy_recipe, or get_recipe. There is no statement of prerequisites or exclusions beyond the inline apiKey note in the schema.

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