Skip to main content
Glama
Sign In
mcp-wendys

mcp-wendys

by markswendsen-code
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

place_order

Finalize your Wendy's order at a specific location with choice of pickup, delivery, or drive-thru, and payment method. Optionally schedule a time.

Instructions

Place the current order at a selected Wendy's location.

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": {
      "location_id": "<location_id>",
      "order_type": "<order_type>",
      "payment_method": "<payment_method>"
    },
    "name": "place_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_typeYesHow to receive the order
location_idYesThe location ID from find_nearby_locations
payment_methodYesPayment method (e.g., 'credit_card', 'apple_pay', 'wendys_rewards')
scheduled_timeNoOptional scheduled pickup/delivery time (e.g., '2:30 PM', 'ASAP')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
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 disclosing behavior. It doesn't mention side effects such as charging the payment method, order irreversibility, or requirements like location operating hours. The description simply states what happens without contextualizing the action's consequences.

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, front-loaded sentence with no redundancy. It effectively communicates the core purpose in minimal words, achieving maximum conciseness without sacrificing clarity.

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?

Given the tool's responsibility (placing an order) and the absence of annotations or output schema, the description is incomplete. It fails to mention that the order must already contain items, that payment will be processed, or any post-placement expectations. The single sentence leaves significant operational context unaddressed.

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%, with each parameter having a clear description (e.g., order_type enum, location_id from find_nearby_locations). The tool description adds no additional parameter-level semantics, but the schema sufficiently documents the required and optional parameters, warranting the baseline score.

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 the tool's action ('Place the current order') and specifies the resource ('at a selected Wendy's location'). This distinguishes it from siblings like 'add_to_order' (which adds items) and 'find_nearby_locations' (which finds locations).

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 explicit guidance on when to use this tool versus alternatives. It doesn't mention prerequisites like needing items in the order (from add_to_order) or that this is the final checkout step. Sibling tools exist but are not referenced.

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