Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mcdonalds_item

Fetch a single McDonald's item's published nutrition facts, allergens, ingredients and image using its item ID and matching market country.

Instructions

Get one McDonald's item's nutrition. Returns one McDonald's item's published nutrition detail: the full per-serving nutrient list (calories, protein, carbohydrates, total and saturated fat, trans fat, cholesterol, sodium, fibre, sugars, vitamins and minerals -- 21 values for a Big Mac), each with a stable machine key, a unit and a percent-daily-value where McDonald's prints one; plus the item's marketing description, allergen statement, full ingredient statement and image. Item ids come from GET /mcdonalds/menu and are market-specific, so pass the same country back. Seven markets serve this endpoint, fewer than the eight publishing a menu -- Great Britain has a menu but no nutrition surface. Combo meals legitimately carry no nutrient list. Prices are not available on this surface.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryNoMarket (default us). One of us, ca, au, ie, nz, ch, se. Must match the market the item id came from.
item_idYesMcDonald's numeric product id, from /mcdonalds/menu

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / country / enum
      Added value: +[
+  "us",
+  "ca",
+  "au",
+  "ie",
+  "nz",
+  "ch",
+  "se"
+]
  2. Addedv1.16.2

TDQS

A4.4/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 disclosure burden and does so thoroughly: it lists the return payload (21 nutrient values, descriptions, allergens, ingredients, image) and explicitly states limitations (no prices, combos lack nutrients, market restrictions). This goes well beyond the schema and arms the agent with expectations for edge cases.

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 longer than average but every sentence adds distinct information: payload contents, item id provenance, market constraints, and edge cases. The main purpose is front-loaded, followed by logical details. It could be trimmed slightly, but there is no redundancy.

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?

As a single-item fetch with no output schema and no annotations, the description provides everything an agent needs: the exact return contents, the source of required item_id, country-market coupling, and known limitations (no prices, combos without nutrients, GB unavailable). Nothing critical is missing for correct invocation.

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 input schema already documents both parameters with 100% coverage, so the baseline is 3. The description reinforces that item ids are market-specific and instructs passing the same country back, but adds little semantic detail beyond the schema text. The market-count note is contextual rather than parameter-specific.

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 opens with a specific verb+resource ('Get one McDonald's item's nutrition') and enumerates exactly what is returned: the full nutrient list, marketing description, allergens, ingredients, and image. It clearly positions this as the single-item detail endpoint distinct from menu/list tools. Mentioning that item ids come from /mcdonalds/menu further disambiguates it from siblings.

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?

It tells the agent to obtain item ids from GET /mcdonalds/menu and to pass the same country back, which is a clear precondition. It also specifies market coverage (seven markets, Great Britain excluded) and notes that combo meals carry no nutrient list, helping the agent avoid invalid calls. It doesn't explicitly name sibling tools, but the workflow guidance is sufficient.

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