Crawlora MCP

taco_bell_store_menu

Read-only

Taco Bell restaurant's full live catalog in one call by store number: every category and item this specific store carries and displays, with price, calories, and per-store availability, plus the store's current happy-hour window.

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": {
      "store_number": "<store_number>"
    },
    "name": "taco_bell_store_menu"
  }
}

Input Schema

Name	Required	Description	Default
`store_number`	Yes	Required. Taco Bell store number, from /taco-bell/stores.

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 7, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description still adds real context beyond them: the data is live, availability is resolved per store, and the response includes prices, calories and a happy-hour window. It does not discuss caching, rate limits, or staleness of the happy-hour window.

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?

One dense sentence that front-loads the resource and scope before enumerating returned fields. Every clause carries information, though the field list (price, calories, availability, happy hour) runs a bit long.

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-value explanation is not strictly required, yet the description usefully previews the payload. For a single-parameter read tool with full schema coverage and an output schema, nothing essential is missing; only explicit sibling routing 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 coverage is 100% and the single parameter is documented in the schema with a pointer to /taco-bell/stores. The description only restates 'by store number' without adding format, validation, or lookup guidance beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource (retrieves the store's full catalog) and pins the scope to a single store via store number, which meaningfully separates it from the chain-wide taco_bell_menu. It never names a sibling tool, so the agent must infer the distinction from phrasing rather than an explicit pointer.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: 'full live catalog in one call' suggests this is the bulk-retrieval option versus making multiple narrower calls, and the store_number requirement implies /taco-bell/stores must be called first. There is no explicit when-to-use, when-not-to-use, or named alternative against taco_bell_menu or taco_bell_categories.

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.