Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

taco_bell_app_menu

Fetch a Taco Bell restaurant's complete app-ordering catalog by store number, including all categories, products, combos with slot choices, and daypart availability.

Instructions

Get one Taco Bell restaurant's full app-ordering catalog, combos included. Returns one Taco Bell US restaurant's complete app-ordering catalog by store number: every category, every individually orderable product, AND every combo (kind "bundle") it carries. This is the only endpoint in this family that publishes combos at all -- each one resolved down to its full slot composition (choices[], each with min/max selections and the product codes it defaults to when not customized), not just a name and price. Also returns the store's named ordering windows (dayparts) and, per item, which dayparts it is orderable in. Store numbers come from GET /taco-bell/stores.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
store_numberYesTaco Bell store number, from /taco-bell/stores

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

TDQS

A4.1/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden. It discloses rich return behavior: full category/product/combo coverage, combo slot composition with min/max selections and default product codes, plus named dayparts and per-item daypart availability. It omits any auth, rate-limit, or error behavior, keeping it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the first two sentences are largely redundant, both restating 'full/complete app-ordering catalog.' The remaining sentences earn their place by detailing combo composition and dayparts, but the repetition costs it conciseness.

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 must explain the return shape, and it does so thoroughly: categories, individually orderable products, combos as kind 'bundle' with slot composition, and dayparts with per-item availability. Nothing an agent needs to call this single-parameter read correctly is missing.

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% for the single store_number parameter, so the schema already documents its type and meaning, establishing the baseline of 3. The description adds only the clarifying detail that the store is a US restaurant and where to source the number, which reinforces but does not extend the schema.

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 (Get) and resource (one Taco Bell restaurant's full app-ordering catalog) with explicit scope (combos included). It also distinguishes itself from siblings by declaring it is 'the only endpoint in this family that publishes combos at all,' giving clear differentiation against taco_bell_menu and taco_bell_store_menu.

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?

Gives the prerequisite for the single input ('Store numbers come from GET /taco-bell/stores') and implies the selection condition via the combos-only claim. It stops short of explicit when-not guidance or a direct comparison to taco_bell_store_menu, so it is clear context rather than full routing.

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