Skip to main content
Glama
Sign In
Burger King MCP Server

Burger King MCP Server

by markswendsen-code
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

search_menu

Search the Burger King menu by keyword or category and retrieve matching items with prices and descriptions.

Instructions

Search the Burger King menu by keyword or category. Returns matching menu items with prices and descriptions.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_menu"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoSearch query (e.g., 'chicken', 'burger', 'fries')
categoryNoFilter by category: burgers, sides, drinks, desserts, breakfast

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries full behavioral disclosure burden. It mentions the return type but omits details like sorting, pagination, or maximum results. The behavior is minimally disclosed; an agent would need to infer read-only nature.

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?

The description is a single sentence that conveys all essential information without redundancy. It is front-loaded with the tool's purpose and includes return details efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of an output schema, the description partially explains return values but fails to address important details like result limits, sorting, or whether both 'query' and 'category' can be combined. The completeness is adequate for a basic search but leaves gaps.

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 both parameters are already well-documented. The description adds only a high-level mapping ('by keyword or category'), which does not provide additional semantic value beyond the schema.

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 the verb 'Search', the resource 'the Burger King menu', and the methods 'by keyword or category'. It also specifies the return value ('matching menu items with prices and descriptions'), which distinguishes it from sibling tools like 'get_item_details' or 'view_cart'.

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 does not provide guidance on when to use this tool versus its siblings. For example, it does not mention that 'get_item_details' should be used for detailed information on a single item. Context is implied by the tool's name, but no explicit usage instructions are given.

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

Deploy Server

Other Tools