Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mcdonalds_menu

Retrieve McDonald's menu category items with ids, names, URLs, and images. Pair a market-specific category slug with its country to get item IDs for full nutrition lookups.

Instructions

List one McDonald's menu category's items. Returns the items in one McDonald's menu category: each item's numeric id, name, product page URL and image. The item id is what GET /mcdonalds/item takes for full nutrition. Category slugs come from GET /mcdonalds/categories and must be paired with the country they came from -- both slugs and item ids are market-specific. Prices are not available; McDonald's does not publish them on this surface. A calorie label is included per item where the category page prints one, which is often blank.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryNoMarket (default us). One of us, ca, gb, au, ie, nz, ch, se. Must match the market the slug came from.
categoryYesCategory slug from /mcdonalds/categories

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden of behavioral disclosure. It reveals that prices are not available ('McDonald's does not publish them on this surface') and that calorie labels are often blank, which are important limitations. It also notes market-specific slugs/ids, but doesn't cover pagination or output format details.

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 three sentences, each adding distinct value: purpose plus return fields, id linkage and prerequisite, then data availability caveats. It's front-loaded and efficient with no redundancy, achieving strong clarity without bloat.

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

Completeness4/5

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

Given two parameters, no output schema, and no annotations, the description covers the essentials: what the tool returns, how to get required inputs, market-specificity, and data limitations. It omits potential pagination or error scenarios, but for a simple list tool this is reasonably complete.

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 coverage is 100% – both country and category have descriptive text including the enum for country. The description adds a note about pairing slugs with country, but this is also reflected in the country parameter description. It doesn't significantly extend beyond the schema, so a baseline 3 is appropriate.

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 'List one McDonald's menu category's items,' which clearly states the verb, resource, and scope. It contrasts with siblings like mcdonalds_categories (list categories) and mcdonalds_item (full nutrition) by specifying it returns items with id, name, URL, and image for a single category.

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 explicitly instructs that category slugs come from GET /mcdonalds/categories and must be paired with the matching country, and that item ids are used by GET /mcdonalds/item for nutrition. This gives clear context on how to use the tool and what to do with the output, though it doesn't explicitly name alternative tools for when it shouldn't be used.

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