Skip to main content
Glama

view_menu

Access the complete Chipotle menu to explore available items before placing an order.

Instructions

View the full Chipotle menu. Start here before ordering.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • index.js:86-120 (handler)
    The handler and registration for the 'view_menu' tool, which constructs a markdown representation of the Chipotle menu and returns it as text content.
    server.tool(
      "view_menu",
      "View the full Chipotle menu. Start here before ordering.",
      {},
      async () => {
        const menu = [
          "# Chipotle Menu",
          "",
          "## Entrees",
          ...ENTREES.map((e) => `  - ${e}`),
          "",
          "## Proteins",
          ...PROTEINS.map((p) => `  - ${p}`),
          "",
          "## Rice",
          ...RICES.map((r) => `  - ${r}`),
          "",
          "## Beans",
          ...BEANS.map((b) => `  - ${b}`),
          "",
          "## Toppings (mix and match)",
          ...TOPPINGS.map((t) => `  - ${t}`),
          "",
          "## Sides",
          ...SIDES.map((s) => `  - ${s}`),
          "",
          "## Drinks",
          ...DRINKS.map((d) => `  - ${d}`),
          "",
          "---",
          "Note: Guac and Queso are extra. Always have been. Always will be.",
        ];
        return { content: [{ type: "text", text: menu.join("\n") }] };
      }
    );
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It implies read-only behavior through the verb 'View' but does not describe what data structure is returned, whether the menu is cached/real-time, or any authentication requirements. Adequate but minimal disclosure for an external-facing 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?

Two sentences with zero wasted words. The action ('View the full Chipotle menu') is front-loaded, followed immediately by usage context ('Start here before ordering'). Every word earns its place.

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?

Given the tool's zero-parameter simplicity and lack of output schema, the description adequately covers the essential intent and entry-point guidance. While it could optionally describe the returned menu structure, this omission is minor given the self-evident nature of a 'view_menu' operation.

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 accepts zero parameters. According to evaluation standards, zero-parameter tools receive a baseline score of 4, as there are no parameter semantic gaps to fill.

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 states exactly what the tool does ('View') with a specific resource ('the full Chipotle menu'). The phrase 'full' distinguishes this comprehensive view from sibling tools like 'build_entree' or 'customize_order' which work with specific items.

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 phrase 'Start here before ordering' provides explicit workflow sequencing, indicating this is a prerequisite step before using sibling tools like 'place_order' or 'build_entree'. While it doesn't explicitly name alternatives, it clearly signals when to invoke this tool in the task lifecycle.

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/YoshiSaurus/mcp-otle'

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