Crawlora MCP

burgerking_availability

Read-only

Burger King restaurant real-time per-channel fulfillment status: live open/closed per order channel with current and next windows, distinct from the published weekly schedule.

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_id": "<store_id>"
    },
    "name": "burgerking_availability"
  }
}

Input Schema

Name	Required	Description
`market`	No	Optional. RBI market the store belongs to, one of US, CA. Default US.
`forecast`	No	Optional. Include a multi-day forward schedule per channel. Default false.
`store_id`	Yes	Required. Burger King's numeric store id, from /burgerking/locations.

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

Behavior4/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 real value beyond that by disclosing live per-channel granularity and the current/next-window structure, telling the agent this is dynamic availability rather than a static schedule. It stops short of mentioning rate limits, auth, or freshness windows.

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?

A single front-loaded sentence with zero filler; the core identity (real-time per-channel fulfillment) comes first and the disambiguation against the weekly schedule closes it. Every clause earns its place.

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 not be explained, and the three parameters are fully described in-schema. The description is complete for a read-only availability lookup, with the only minor gap being the absence of usage/routing context for an agent navigating the many burgerking siblings.

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%, so market, forecast, and store_id are fully documented in the schema; the description adds no syntax or format detail beyond what those parameter descriptions already provide. Baseline 3 is appropriate when the schema does all the semantic work.

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?

Names a specific verb+resource (Burger King restaurant real-time per-channel fulfillment status) and enumerates exactly what is returned: live open/closed per order channel with current and next windows. It also explicitly scopes itself apart from the 'published weekly schedule,' so an agent can distinguish live status from a static schedule without opening the schema.

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?

The description implies the usage context (real-time fulfillment checks) and clarifies what it is not, but gives no explicit when-to-use guidance against alternatives such as burgerking_locations or burgerking_menu. No prerequisites or exclusions are stated, so the routing signal is only implied.

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?