Skip to main content
Glama

customize_order

Submit special requests for existing orders to modify items or add instructions. Provide order ID and specific customization details.

Instructions

Make special requests for your order. Results may vary.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
order_idYesThe order ID to customize
requestYesYour special request

Implementation Reference

  • Handler function for the "customize_order" tool.
    async ({ order_id, request }) => {
      const order = orders.find((o) => o.id === order_id);
      if (!order) {
        return {
          content: [
            {
              type: "text",
              text: `Order ${order_id} not found. Can't customize what doesn't exist. That's philosophy.`,
            },
          ],
        };
      }
    
      const responses = [
        `Special request "${request}" has been noted. The line cook nodded solemnly.`,
        `"${request}" - Bold choice. We've alerted the tortilla whisperer.`,
        `Request received: "${request}". Our AI-powered burrito engineer is on it.`,
        `"${request}" - This has never been requested before. You are a pioneer.`,
        `We've forwarded "${request}" to our Chief Guacamole Officer for approval.`,
      ];
    
      const response = responses[Math.floor(Math.random() * responses.length)];
    
      return {
        content: [
          {
            type: "text",
            text: `# Customization Request\n\n**Order:** ${order_id}\n**Request:** ${request}\n\n${response}\n\n> ${getRandomQuip()}`,
          },
        ],
      };
  • index.js:343-349 (registration)
    Registration of the "customize_order" tool with its schema definition.
    server.tool(
      "customize_order",
      "Make special requests for your order. Results may vary.",
      {
        order_id: z.string().describe("The order ID to customize"),
        request: z.string().describe("Your special request"),
      },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Results may vary' vaguely hints at uncertainty but fails to explain what the tool actually does (e.g., whether it modifies order state immediately, submits a request for approval, or notifies staff), nor does it mention side effects, permission requirements, or idempotency.

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 description is appropriately brief with only two sentences and no verbosity. The key purpose is front-loaded in the first sentence. However, the second sentence ('Results may vary.') is vague and does not earn its place effectively, preventing a score of 5.

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 mutation tool with no annotations and no output schema, the description is insufficiently complete. It fails to explain success indicators, failure modes, or what 'customize' entails operationally, leaving developers without critical context for a state-changing operation.

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?

The input schema has 100% description coverage ('The order ID to customize', 'Your special request'), establishing clear semantics for both parameters. The description adds no parameter-specific guidance beyond the schema, which warrants the baseline score of 3 for high-coverage schemas.

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 clear verb ('Make') and resource ('special requests for your order'), establishing what the tool does. However, it does not explicitly differentiate from siblings like 'place_order' or 'build_entree' that may also involve customization, leaving potential ambiguity about whether this modifies existing orders versus creates new ones.

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 provides no guidance on when to use this tool over alternatives like 'place_order' or 'build_entree'. The phrase 'Results may vary' offers no actionable criteria for tool selection and does not clarify prerequisites (e.g., requiring an existing order).

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