Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

wendys_item

Retrieve detailed Wendy's menu item or combo data, including prices, calories, size variants, modifiers, and per-component allergen lists for informed ordering decisions.

Instructions

Get one Wendy's menu item's (or combo's) detail. Returns one item's full detail. A simple item (is_combo false) returns its description, base price, calories, every size/weight variant (e.g. Small/Medium/Large fries, each with its own price and calories, with is_default marking the one Wendy's own page pre-selects), and every modifier component -- default (comes with the item), extra (a paid add-on) and required (the caller must pick one option from a named group, e.g. a salad's dressing) -- each with its own ingredient description and allergen list, since Wendy's publishes allergens per-component rather than as one whole-item field. The top-level allergens field is the union across default components and each required group's default-selected option only. A combo (is_combo true) instead returns combo_slots: its entree/side/drink composition and every product each slot can be built from, since a combo's own price and calories vary by what is chosen. A combo slot's product ids are the same items sold standalone in their own categories -- call this endpoint again on one of those for its own full component/allergen detail. Category and item slugs come from GET /wendys/categories and GET /wendys/menu.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemYesItem slug from /wendys/menu's items[].slug
categoryYesCategory slug from /wendys/categories

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations, the description carries the full burden, and it is outstanding: it explains the simple-item vs combo branching, variant pricing with is_default, modifier component types (default/extra/required), per-component allergen structure, top-level allergen union semantics, and combo slot behavior. This is far beyond a generic 'returns item details' statement.

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 front-loaded with the core purpose and then logically structured around simple items vs combos. It is long, but the complexity justifies most of the length. There is minor redundancy in 'Get one... detail' followed by 'Returns one item's full detail,' which costs a point.

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

Completeness5/5

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

Given no output schema, the description fully compensates by explaining what the response contains for both simple items and combos, including relevant field concepts, allergen semantics, and how to traverse combo slot product IDs. An agent can call this tool correctly and understand the returned data without additional context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds value by clarifying that item slugs originate from the menu endpoint and that combo slot product IDs are also accepted as item values, while category slugs come from the categories endpoint. This extra guidance helps the caller correctly invoke the tool beyond the schema descriptions.

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 opens with a specific verb and resource: 'Get one Wendy's menu item's (or combo's) detail,' and clearly identifies the tool as a single-item detail endpoint. It does not explicitly name sibling tools or contrast itself with wendys_menu or wendys_nutrition, though the slug-source sentence implies the surrounding workflow.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context about when this endpoint is appropriate: it returns full item/combo detail, and combo slot product IDs can be re-fetched by calling this endpoint again. It also tells the caller where to obtain the required slug parameters (wendys/categories and wendys/menu). However, it does not explicitly state when to prefer a sibling tool over this one.

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