Skip to main content
Glama

Little Works

list_recipes

List cookable or priced recipes / cook starters.

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": "list_recipes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

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?

With no annotations supplied, the description carries the full burden: it does not state that this is a read-only operation, whether results are paginated or capped, whether the "cookable or priced" distinction is a filter or a property of returned items, or what happens when no limit is given. Only the word "List" weakly signals a read operation.

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?

One short sentence with no filler, so nothing is wasted, but the compression comes at the cost of clarity — the slash-separated phrasing reads as ambiguous rather than efficient. It is front-loaded but under-specified rather than precise.

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?

With no annotations, no output schema, and an undocumented parameter, the description would need to do considerably more work than one fragment. An agent cannot tell the result shape, whether cook starters are included, or how limit behaves, which is inadequate even for a simple list tool.

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?

The single parameter (limit) has 0% schema description coverage, so the description had to compensate and says nothing about it — no default, range, or what happens when omitted. The "cookable or priced" wording is not mapped to any parameter, leaving the only input undocumented in both places.

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 description names a verb ("List") and a resource ("recipes"), but the qualifier "cookable or priced recipes / cook starters" muddles what is actually listed, and the slash construction implies the tool may also return cook starters, which is a separate sibling tool. An agent can guess the general area but cannot confidently predict what set of records comes back.

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?

There is no statement of when to use this tool versus alternatives, and notably nothing distinguishing it from the sibling list_cook_starters despite the description mentioning "cook starters" itself. Usage is only implied by the verb "List".

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