Crawlora MCP

taco_bell_nutrition

Read-only

Fetch a Taco Bell item's full nutrition panel, including vitamins and minerals, serving size, and allergens, with optional ingredients. Use taco_bell_product for customization and product details or taco_bell_menu and taco_bell_categories to browse items.

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_nutrition"
  }
}

Input Schema

Name	Required	Description
`product`	Yes	Required. Product slug, the last segment of a /food/<category>/<product> URL.
`category`	Yes	Required. Category slug from /taco-bell/categories.
`include_ingredients`	No	Optional. Include the full ingredient statement. Default false -- it is long.

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.2/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 safety is covered. The description adds the returned content (nutrition panel fields) and the schema notes ingredients are long, but it discloses nothing about auth, rate limits, or freshness beyond that. Modest added value over annotations.

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 the primary purpose, followed by sibling routing. No wasted words.

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?

With an output schema present, return values needn't be explained, and annotations cover safety. The description is complete enough to select and call the tool correctly; only minor behavioral detail is absent.

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%, so product, category, and include_ingredients are already documented in the schema. The description adds no parameter syntax or format detail beyond what the schema provides; 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?

The description states a specific verb (Fetch) and resource (Taco Bell item's full nutrition panel) and enumerates the contents — vitamins, minerals, serving size, allergens, optional ingredients. It clearly distinguishes itself from sibling tools by naming them for other purposes.

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?

It explicitly routes the agent: use taco_bell_product for customization/product details and taco_bell_menu or taco_bell_categories to browse. This is a clear when-to-use-this vs when-to-use-alternatives statement.

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?