Skip to main content
Glama

Browse CookUnity Menu

cookunity_get_menu
Read-onlyIdempotent

Browse and filter CookUnity meal delivery menus by date, category, diet, price, and rating with pagination support.

Instructions

Browse available meals for a delivery date with optional filters and pagination.

Args:

  • date (string, optional): YYYY-MM-DD delivery date. Defaults to next Monday.

  • category (string, optional): Filter by category (e.g. 'Bowls', 'Protein+')

  • diet (string, optional): Filter by diet tag (e.g. 'vegan', 'gluten-free')

  • max_price (number, optional): Max price in dollars

  • min_rating (number, optional): Min rating 0-5

  • limit (number): Results per page, default 20, max 50

  • offset (number): Pagination offset, default 0

  • response_format ('markdown'|'json'): Output format

Returns (JSON): { total, count, offset, has_more, next_offset?, categories, meals[] } Returns (Markdown): Formatted meal cards with chef, price, rating, nutrition

Examples:

  • Browse next week's menu: {}

  • Vegan meals under $12: { diet: "vegan", max_price: 12 }

  • Page 2: { offset: 20 }

Error Handling:

  • Invalid date format returns validation error

  • API failures return actionable error with status code

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoDelivery date in YYYY-MM-DD format (must be a Monday). Defaults to next Monday if omitted.
categoryNoFilter by category title (e.g. 'Bowls', 'Protein+')
dietNoFilter by diet tag (e.g. 'gluten-free', 'vegan', 'dairy-free')
max_priceNoMaximum price filter in dollars
min_ratingNoMinimum rating filter (0-5)
limitNoResults per page (max 50)
offsetNoNumber of results to skip for pagination
response_formatNoOutput format: 'markdown' for human-readable or 'json' for structured datamarkdown
Behavior4/5

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

The description adds valuable behavioral context beyond annotations: it explains pagination behavior (limit/offset), output format options (JSON vs Markdown), default values (next Monday, limit 20), and error handling specifics. While annotations cover safety (readOnly, non-destructive), the description provides practical implementation details that help the agent use the tool correctly.

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?

The description is perfectly structured and front-loaded: the first sentence captures the core functionality, followed by logically organized sections (Args, Returns, Examples, Error Handling). Every section adds value with zero redundancy. The examples are specific and illustrative without being verbose.

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

Completeness5/5

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

Given the tool's complexity (8 parameters, filtering, pagination, dual output formats) and absence of an output schema, the description provides complete context. It explains return formats for both JSON and Markdown, documents error handling, provides practical examples, and covers all behavioral aspects needed for effective use. The annotations complement this with safety information.

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?

With 100% schema description coverage, the baseline is 3. The description adds meaningful context by grouping parameters logically (optional filters, pagination, output format), providing concrete examples of parameter values (e.g., 'vegan', 'gluten-free', $12), and explaining the relationship between parameters in the examples. This enhances understanding beyond the schema's technical specifications.

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

Purpose5/5

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

The description clearly states the tool's purpose with specific verb ('Browse') and resource ('available meals'), distinguishing it from siblings like 'cookunity_get_meal_details' (single meal) and 'cookunity_search_meals' (different search approach). It explicitly mentions delivery date and optional filters, making the scope unambiguous.

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

Usage Guidelines4/5

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

The description provides clear context for when to use this tool (browsing meals for a delivery date with filters), and the examples illustrate common use cases. However, it doesn't explicitly state when NOT to use it or mention alternatives like 'cookunity_search_meals' for different search approaches, which would be helpful for sibling differentiation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ggonzalezaleman/cook-unity-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server