Burger King MCP Server

find_locations

Search for nearby Burger King restaurants by address or ZIP code. Get location names, addresses, and hours.

Instructions

Find nearby Burger King locations by address or ZIP code. Returns location names, addresses, and hours.

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": {
      "address": "<address>"
    },
    "name": "find_locations"
  }
}

Input Schema

Name	Required	Description	Default
`address`	Yes	Address, city, or ZIP code to search near
`radius_miles`	No	Search radius in miles (default: 5)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Apr 3, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Description discloses return fields (names, addresses, hours) beyond schema input, but lacks details on result limits, error handling, or behavior when no locations are found.

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 verb and resource, every word earns its place. No fluff.

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?

For a simple two-parameter tool with no output schema, the description sufficiently covers purpose and return values. Could mention default radius, but schema already provides that.

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% with descriptions for both parameters. The description's mention of 'address or ZIP code' slightly overlaps with schema, adding no significant new meaning.

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 clearly states it finds nearby Burger King locations by address or ZIP code, listing returned data (names, addresses, hours). This distinguishes it from siblings like search_menu or get_item_details.

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?

No guidance on when to use this tool vs alternatives. While the purpose is clear, it lacks explicit when-to-use or when-not-to-use context, leaving the agent to infer based on tool naming.

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

Deploy Server