Skip to main content
Glama
Sign In
mcp-wendys

mcp-wendys

by markswendsen-code
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

add_to_order

Add items to your Wendy's mobile order cart, with options for quantity and customizations such as no pickles or extra cheese.

Instructions

Add an item to the current mobile order cart.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "item_name": "<item_name>"
    },
    "name": "add_to_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
quantityNoQuantity to add (default: 1)
item_nameYesName of the menu item to add
customizationsNoOptional customizations (e.g., 'no pickles', 'extra cheese', 'medium size')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of disclosing side effects. 'Add an item to the current mobile order cart' implies a mutation but does not state whether it requires an existing cart, what happens if the item is unavailable, or if the action is irreversible. It adds minimal context beyond the basic action.

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 a single sentence of ten words, entirely front-loaded with the essential purpose. Every word is necessary, and there is no filler or 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?

For a simple tool with three parameters and full schema descriptions, the description is minimally adequate but lacks contextual details. It does not explain that a 'current order' must exist, or how this step fits into the larger order workflow (search → add → apply offers → place order). The absence of annotations and output schema increases the need for more context, which is not provided.

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 description coverage is 100% for all three parameters (item_name, quantity, customizations), so the baseline is 3. The tool description does not add any meaning beyond the schema; for instance, it does not clarify how item_name maps to menu items or how customizations are formatted.

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 a specific action 'Add an item' to a specific resource 'current mobile order cart'. It distinguishes this tool from siblings like 'place_order' (finalizing) and 'search_menu_items' (discovery), making its purpose unambiguous.

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 relative to alternatives. It does not mention that this should be used after searching for items, before placing an order, or that it requires an active cart. No exclusions or alternative recommendations are given.

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

Deploy Server

Other Tools