Crawlora MCP

taco_bell_menu

Read-only

Fetch Taco Bell US menu categories and items with prices, calories, customization, and availability. Use taco_bell_app_menu or taco_bell_store_menu for their specific menu views, or taco_bell_nutrition for nutrition facts.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "category": "<category>"
    },
    "name": "taco_bell_menu"
  }
}

Input Schema

Name	Required	Description	Default
`category`	Yes	Required. Category slug from /taco-bell/categories.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful context on the payload (prices, calories, customization, availability) and the US-only scoping, but says nothing about pagination, freshness, or auth. Reasonable but not rich for an annotated tool.

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?

Two sentences, front-loaded with purpose before alternatives, no wasted words. The routing information is compact and actionable.

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?

An output schema exists, so return values need no explanation, and the description still summarizes what comes back. Sibling routing is present and the required param source is referenced. Only minor gaps remain (e.g., what a category slug looks like), so the definition is essentially 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% and the single category param is documented as a required slug from /taco-bell/categories, so the schema carries the burden. The description adds no slug syntax or format detail beyond what the schema already provides, so baseline 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?

States a specific verb (Fetch) plus resource and scope (Taco Bell US menu categories and items), and enumerates the returned dimensions (prices, calories, customization, availability). It also names the sibling tools it is not, so an agent can distinguish it from taco_bell_app_menu, taco_bell_store_menu, and taco_bell_nutrition 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?

Explicitly routes the agent to alternatives, naming taco_bell_app_menu / taco_bell_store_menu for specific menu views and taco_bell_nutrition for nutrition facts. It stops short of an explicit statement of when this general US menu is the right choice versus those, but the implied default is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?