Skip to main content
Glama

place_order

Place a complete Chipotle order by selecting your entree, protein, rice, beans, toppings, and optional sides and drinks.

Instructions

Place a complete Chipotle order. Provide your entree details, optional sides, and drinks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entreeYesType of entree
proteinYesChoice of protein
riceYesChoice of rice
beansYesChoice of beans
toppingsYesList of toppings
double_proteinNoDouble protein
sidesNoOptional sides
drinksNoOptional drinks
nameYesName for the order

Implementation Reference

  • The 'place_order' tool implementation handles the complete ordering flow, including price calculation, order creation with simulated state, and generating a confirmation receipt.
    server.tool(
      "place_order",
      "Place a complete Chipotle order. Provide your entree details, optional sides, and drinks.",
      {
        entree: z.enum(ENTREES).describe("Type of entree"),
        protein: z.enum(PROTEINS).describe("Choice of protein"),
        rice: z.enum(RICES).describe("Choice of rice"),
        beans: z.enum(BEANS).describe("Choice of beans"),
        toppings: z
          .array(z.enum(TOPPINGS))
          .min(0)
          .max(TOPPINGS.length)
          .describe("List of toppings"),
        double_protein: z.boolean().default(false).describe("Double protein"),
        sides: z.array(z.enum(SIDES)).default([]).describe("Optional sides"),
        drinks: z.array(z.enum(DRINKS)).default([]).describe("Optional drinks"),
        name: z.string().describe("Name for the order"),
      },
      async ({ entree, protein, rice, beans, toppings, double_protein, sides, drinks, name }) => {
        let price = { Burrito: 10.75, Bowl: 10.75, "Tacos (3)": 10.75, Salad: 10.75, Quesadilla: 11.5, "Kid's Meal": 6.25 }[entree] || 10.75;
        if (double_protein) price += 3.75;
        if (toppings.includes("Guacamole")) price += 2.95;
        if (toppings.includes("Queso Blanco")) price += 1.65;
    
        const sidePrices = { Chips: 1.95, "Chips & Guac": 5.45, "Chips & Queso": 4.25, "Chips & Salsa": 2.95 };
        for (const side of sides) price += sidePrices[side] || 0;
    
        const drinkPrice = 2.65;
        price += drinks.length * drinkPrice;
    
        const tax = price * 0.0825;
        const total = price + tax;
    
        const orderId = generateOrderId();
        const waitTime = getWaitTime();
    
        const order = {
          id: orderId,
          name,
          entree,
          protein: double_protein ? `Double ${protein}` : protein,
          rice,
          beans,
          toppings,
          sides,
          drinks,
          subtotal: price.toFixed(2),
          tax: tax.toFixed(2),
          total: total.toFixed(2),
          status: "Being Prepared",
          estimatedWait: waitTime,
          placedAt: new Date().toISOString(),
        };
    
        orders.push(order);
    
        const receipt = [
          "# Order Confirmed!",
          "",
          `**Order #${orderId}** for **${name}**`,
          "",
          "---",
          `**${entree}**`,
          `  Protein: ${order.protein}`,
          `  Rice: ${rice}`,
          `  Beans: ${beans}`,
          `  Toppings: ${toppings.length > 0 ? toppings.join(", ") : "None"}`,
          "",
          ...(sides.length > 0 ? ["**Sides:** " + sides.join(", "), ""] : []),
          ...(drinks.length > 0 ? ["**Drinks:** " + drinks.join(", "), ""] : []),
          "---",
          `Subtotal: $${order.subtotal}`,
          `Tax: $${order.tax}`,
          `**Total: $${order.total}**`,
          "",
          `Estimated wait: ~${waitTime} minutes`,
          "",
          `> ${getRandomQuip()}`,
        ];
    
        return { content: [{ type: "text", text: receipt.join("\n") }] };
      }
    );
Behavior2/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 of behavioral disclosure. It fails to mention critical transactional behaviors: whether this charges money, if the order is immediate or scheduled, whether it is reversible/cancellable, or what confirmation/tracking mechanism follows. 'Place' implies commitment but lacks transparency about side effects.

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?

The two-sentence structure is appropriately brief and front-loaded with the core action. However, the second sentence spends space listing parameter categories that are already obvious from the schema, rather than providing usage constraints or behavioral warnings.

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?

As a 9-parameter transactional tool with no annotations and no output schema, the description is incomplete. It omits critical context for an order placement operation: payment implications, order confirmation details, pickup/delivery logistics, or error handling. For a destructive financial transaction, this lack of behavioral context is a significant gap.

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?

With 100% schema description coverage, the schema already documents all 9 parameters clearly. The description provides only a high-level grouping ('entree details, optional sides, and drinks') without adding syntax guidance, validation rules, or semantic relationships between parameters (e.g., that certain proteins cost extra with double_protein). Baseline 3 is appropriate.

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?

The description uses a specific verb ('Place') and clear resource ('Chipotle order'), and the word 'complete' helps distinguish this from sibling tools like 'build_entree' or 'customize_order'. However, it could more explicitly clarify the distinction between assembling an order versus finalizing/committing it.

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 mentions what inputs to provide ('entree details, optional sides, and drinks') but offers no guidance on when to use this tool versus siblings like 'build_entree', 'customize_order', or 'bowl_vs_burrito_decision_engine'. No prerequisites, conditions, or alternatives are mentioned.

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