Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

subway_menu

Fetch a Subway store's full menu by store ID to get categories, products, sizes, prices, nutrition, and allergens. US stores only.

Instructions

Get one Subway store's full menu. Returns one Subway store's complete menu: every category, every product, and for each purchasable size (Footlong, 6-inch, etc.) its price, full nutrition panel (calories, fat, sodium, protein and more) and allergen disclosures. Store IDs come from a GET /subway/store result's store_id field. This endpoint currently covers US stores only: the menu is not available for non-US stores, which return 404 -- see GET /subway/combos for the bundle/combo categories that are available in other markets. Categories carry is_main_category: true for human-browsable menu sections (Sandwiches, Drinks, Salads, ...) and false for Subway's own internal build/customization groupings, which are included for completeness but are not meant to be shown as menu sections on their own.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
store_idYesStore ID from a /subway/store result's store_id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses a lot of behavior: the US-only coverage constraint, the 404 failure mode for non-US stores, the is_main_category flag semantics distinguishing browsable sections from internal groupings, and the full return contents. It does not mention auth or rate limits, but for a read endpoint this is strong coverage.

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?

Front-loaded with the core return description, then the store_id sourcing, the geographic limitation, and the category-flag semantics. Every sentence carries useful information, though it is longer than strictly necessary and the is_main_category detail could be trimmed.

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?

With no output schema, the description takes on the burden of explaining return values, and it does so fully: categories, products, per-size pricing, nutrition panels, and allergen disclosures, plus the category flag meaning. An agent has everything needed to call and interpret this 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 description coverage is 100% and the single parameter is already documented in the schema ('Store ID from a /subway/store result's store_id'). The description repeats the same provenance detail, adding no new syntax, format, or validation meaning beyond the schema. 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?

States a specific verb and resource ('Get one Subway store's full menu') and immediately scopes it against siblings by naming the store_id source (GET /subway/store) and the non-US alternative (GET /subway/combos). An agent can distinguish it from subway_combos and subway_store without opening any schema.

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 states the precondition (store IDs come from a /subway/store result's store_id field), the limitation (US stores only; non-US returns 404), and routes to the alternative (subway_combos) for other markets. When-to-use, when-not-to-use, and the alternative are all present.

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