Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

wendys_nutrition

Retrieve a Wendy's menu item's complete nutrition-facts panel — calories, fat, sodium, carbs, protein, vitamins, minerals, and allergens — as real numbers, using category and item slugs.

Instructions

Get one Wendy's menu item's full nutrition-facts panel. Returns one item's (or combo's) complete nutrition-facts panel -- calories, fat, cholesterol, sodium, carbohydrate, protein, vitamins and minerals -- as real numbers, plus declared allergens. A simple item's panel is for its default configuration (default bun/size, default condiments, no extras, no required-group substitutions). A combo's panel (is_combo true) is the combined total across every slot's default option in one request, the same way a caller building the full order would sum it themselves -- combo_selections lists which option each slot was computed for. GET /wendys/item and GET /wendys/menu only ever carry a calorie count, because that is all Wendy's own menu pages themselves publish inline; the full panel is fetched separately by Wendy's own "Nutrition" tab, and this endpoint resolves and calls that same source so a caller does not have to reverse-engineer it. A nutrient Wendy's does not publish is omitted from the response rather than reported as zero. 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 -- a combo slug is accepted
categoryYesCategory slug from /wendys/categories

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so thoroughly. It discloses that simple items use default configuration, combos are combined totals, missing nutrients are omitted rather than zero, and it resolves the same source as Wendy's Nutrition tab. This is far beyond typical disclosure.

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?

Although lengthy, every sentence adds necessary context—defaults, combo behavior, source, and missing nutrients. It is front-loaded with the primary purpose and structured logically, with no redundant fluff.

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 there is no output schema, the description fully explains the expected return: calories, fat, cholesterol, sodium, carbohydrate, protein, vitamins, minerals, and allergens. It also covers edge cases (combo_selections, omitted nutrients) and points to where slugs originate, making it complete for an agent to call correctly.

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 schema already has 100% coverage with descriptions referencing the source endpoints and accepting combo slugs. The tool description repeats this but adds no new parameter-specific meaning beyond what the schema provides, so it does not significantly exceed the baseline.

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 retrieves a full nutrition-facts panel for a single Wendy's menu item, specifying the exact resource and verb. It distinguishes itself from sibling tools (wendys_item, wendys_menu) by noting they only provide calorie counts, making the 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 Guidelines5/5

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

Explicitly contrasts with GET /wendys/item and GET /wendys/menu, stating they only carry calorie count, so if a full panel is needed, this tool is the choice. It also clarifies when to use it for combos and default configurations, giving clear context.

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