Skip to main content
Glama
Sign In
mcp-wendys

mcp-wendys

by markswendsen-code
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

apply_offer

Apply a promotional offer or deal code to the current order to receive the applicable discount.

Instructions

Apply a promotional offer or deal code to the current order.

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": {
      "offer_code": "<offer_code>"
    },
    "name": "apply_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
offer_codeYesThe offer or promo code to apply (e.g., 'FROSTY1', 'MOBILE10')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations, the description must carry all behavioral context, but it only states the action without disclosing side effects, prerequisites, or error behavior, such as whether it modifies the order total or requires an active order.

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 precise sentence that conveys the action without any redundant words.

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?

The tool is simple with one parameter and no output schema, but the description omits important contextual details like the need for a current order or the effect of an invalid code, making it minimally adequate.

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 parameter is fully described in the schema with examples, and the description adds no additional parameter semantics; per rubric, high schema coverage gives a baseline of 3.

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 uses the specific verb 'apply' with the resource 'promotional offer or deal code' and clearly states it applies to the current order, distinguishing it from sibling tools like add_to_order or place_order.

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?

No explicit when-to-use guidance or alternatives are given, but the action is self-evident; it is implied that this is used when a customer has an offer code to apply to their order.

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