Skip to main content
Glama
Sign In
recipe-mcp-server

recipe-mcp-server

by OpenCode-Projects-AtlasRearden8
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_recipes

Lists every recipe in your collection with ID, title, servings, and tags so you can review available recipes and choose what to cook.

Instructions

List every recipe in the collection (id, title, servings, tags).

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, and it only implies read-only via 'List'. It discloses nothing about ordering, pagination, result-size limits, or what happens on an empty or very large collection, which are the real behavioral questions for an enumerate-everything tool.

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?

A single sentence with no waste, front-loading the action and scope before the returned-field list in parentheses. Nothing could be cut without losing information.

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?

For a no-parameter list tool with no output schema, naming the returned fields (id, title, servings, tags) covers the main gap an agent would otherwise have. Missing ordering and pagination behavior keeps it from being complete for a potentially large collection.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline is 4. The parenthetical does add value by naming the fields returned rather than inputs, which is a reasonable substitute use of the space.

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

Purpose4/5

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

States a specific verb ('List') and resource ('every recipe in the collection'), which an agent can distinguish from search_recipes or get_recipe by the word 'every'. It does not explicitly name a sibling alternative, so it stops short of full differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: 'every recipe' suggests an unfiltered enumeration versus the filtered search_recipes sibling, but the description never says when to prefer this tool or when another is better. No prerequisites or exclusions are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools