Skip to main content
Glama

check_order_status

Check the status of a previously placed Chipotle order by providing the order ID to track its progress and delivery details.

Instructions

Check the status of a previously placed order.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
order_idYesThe order ID (e.g. CHIP-1001)

Implementation Reference

  • Handler logic for check_order_status tool, which looks up an order by ID and returns its status.
    async ({ order_id }) => {
      const order = orders.find((o) => o.id === order_id);
      if (!order) {
        return {
          content: [
            {
              type: "text",
              text: `Order ${order_id} not found. Either it doesn't exist or you ate it already.`,
            },
          ],
        };
      }
    
      // Simulate progress
      const elapsed = (Date.now() - new Date(order.placedAt).getTime()) / 1000;
      let status;
      if (elapsed > 120) {
        status = "Ready for Pickup!";
      } else if (elapsed > 60) {
        status = "Almost done - wrapping your burrito with love";
      } else if (elapsed > 30) {
        status = "Scooping rice with surgical precision";
      } else {
        status = "In the queue - your tortilla is being spiritually prepared";
      }
      order.status = status;
    
      const lines = [
        `# Order Status: ${order.id}`,
        "",
        `**Name:** ${order.name}`,
        `**Status:** ${status}`,
        `**Ordered:** ${order.placedAt}`,
        `**Total:** $${order.total}`,
        "",
        `> ${getRandomQuip()}`,
      ];
    
      return { content: [{ type: "text", text: lines.join("\n") }] };
    }
  • index.js:260-265 (registration)
    Registration of the check_order_status tool.
    server.tool(
      "check_order_status",
      "Check the status of a previously placed order.",
      {
        order_id: z.string().describe("The order ID (e.g. CHIP-1001)"),
      },
Behavior2/5

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

With no annotations provided, the description carries full behavioral disclosure burden. While 'Check' suggests a read operation, the description fails to disclose what status values are returned, whether this operation is idempotent, or if there are rate limits on checking status.

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?

Single front-loaded sentence with zero waste. Every word earns its place by defining the action, target, and scope without redundancy.

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

Completeness3/5

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

Adequate for a single-parameter tool with full schema coverage, but lacks description of return values or status enumerations (e.g., pending, ready, completed) which would help given no output schema exists.

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?

Schema coverage is 100% (order_id fully documented with example format CHIP-1001), establishing baseline 3. The description adds no parameter-specific context, but none is needed given the schema's completeness.

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?

Clear verb 'Check' and resource 'status of a previously placed order'. The phrase 'previously placed' effectively distinguishes this from the sibling 'place_order' tool by implying this operates on existing orders, though it doesn't explicitly name alternatives.

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?

Provides implied usage context via 'previously placed', suggesting this is for post-purchase tracking. However, lacks explicit when-to-use guidance (e.g., 'Use after place_order') or conditions for when status cannot be retrieved.

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