Crawlora MCP

taco_bell_product

Read-only

Fetch a Taco Bell item with price, images, cross-sells, and its customization choices. Use taco_bell_menu and taco_bell_categories to find items or taco_bell_nutrition for detailed nutrition data.

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>",
      "product": "<product>"
    },
    "name": "taco_bell_product"
  }
}

Input Schema

Name	Required	Description	Default
`product`	Yes	Required. Product slug, the last segment of a /food/<category>/<product> URL.
`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 the content shape (price, images, cross-sells, customization) but says nothing about auth, caching, or rate limits, and the output schema carries the return 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?

Two tightly written sentences, with the primary purpose front-loaded and the alternative-tool routing second. No filler or redundancy.

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 covers purpose plus sibling routing. The only minor gap is that the description never states the precondition for calling it (needing a valid category/product slug), which the schema implies.

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 parameters are documented with their required status and slug derivation from /food/<category>/<product> URLs. The description adds nothing beyond the schema, so the 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') and resource ('a Taco Bell item'), then enumerates the payload (price, images, cross-sells, customization choices). It also implicitly distinguishes itself from the menu/categories/nutrition siblings by naming what they are for.

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: taco_bell_menu and taco_bell_categories 'to find items' and taco_bell_nutrition 'for detailed nutrition data'. This makes clear this tool is the detail fetch, though it never states the precondition that a category+product slug must already be known.

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?