Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fiveguys_menu

List Five Guys menu categories and items, including descriptions, calories, and images. Filter by category or language to display the full menu or one category's items.

Instructions

List Five Guys menu categories and items. Returns Five Guys' public menu content: every category (Burgers, Fries, Shakes, Hot Dogs, Sandwiches, Drinks, Toppings) -- each with its own short description and cover image, plus its items' name, description, calories, and image -- or one category's items when category is given. Five Guys publishes no per-item price on this surface -- pricing is store-scoped and lives only behind its ordering flow, which this endpoint does not cover. Available in English (default) and Spanish via lang. Calories are shown exactly as published: a single value for most items, or a range (e.g. fries' "530-1100") for build-your-own items whose calories vary by size and toppings. Some items (drink categories, a few build-your-own items) publish no calorie figure at all; their calories field is omitted rather than estimated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNoOptional. Content language: en (default) or es.
categoryNoOptional. One category slug to return only that category's items. Omit to return the full menu across every category. With lang=en (the default) one of: burgers, fries, shakes, dogs, sandwiches, drinks, toppings. With lang=es the slugs differ -- read them from a lang=es response's categories[].slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / lang / enum
      Added value: +[
+  "en",
+  "es"
+]
  2. Addedv1.16.2

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral disclosure burden. It discloses the return structure, calorie representation (single value, range, or omitted rather than estimated), and the absence of per-item prices, which are valuable quirks beyond a generic menu listing. It does not discuss error handling or rate limits, but for a public read-only menu surface this is sufficient.

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 adds detail in a logical order: content, exclusions, language, calorie formatting. It is slightly long (about 150 words) but every sentence conveys a distinct fact an agent needs; no fluff.

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?

For a tool with two optional parameters and no output schema, the description covers what is returned (categories/items and their fields), how calories behave, that prices are unavailable, and how language selection works. It leaves out only minor edge-case behavior (e.g., invalid category slugs), so an agent has enough to call it 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?

Schema coverage is 100% and both parameters already carry rich descriptions in the schema (default lang, category slugs per language, omit behavior). The description repeats the language default and category behavior but adds little beyond what the schema states, so the baseline of 3 applies.

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 and resource ('List Five Guys menu categories and items') and enumerates the exact content returned (categories, items, names, descriptions, calories, images). It also disambiguates from siblings like fiveguys_ordering_menu by explicitly stating pricing is not covered, so an agent can distinguish this menu endpoint from the ordering flow without opening schemas.

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 clearly states the tool returns public menu content and explicitly carves out pricing as living behind the ordering flow, giving an implicit when-not-to-use. It explains the optional category filter and language behavior, providing enough context for selecting this tool over a store/nutrition/ordering endpoint, though it doesn't name the sibling tool explicitly.

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