Skip to main content
Glama

get_big_mac_index

The Fast Food Index Big Mac index: the national median Big Mac price across priced US McDonald's restaurants, its range and extremes, and the median by state with each state vs the national figure. Data collected weekly from McDonald's own ordering system.

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": "get_big_mac_index"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and does add real behavioral context: the data comes from McDonald's own ordering system and is collected weekly, and the returned aggregates (median, range, extremes, per-state medians) are disclosed. What it does not state is whether results are a live snapshot or cached, or how the extremes/range are defined.

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?

A single dense sentence with no filler, and the primary subject (national median Big Mac price) is front-loaded before the geographic breakdown and provenance. The long comma-separated list of returned elements is slightly hard to parse but every clause adds content.

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 zero-parameter read tool with no output schema and no annotations, the description supplies the key things an agent needs: what aggregates come back, at what granularity, and how fresh the data is. Field names and units of the returned structure remain unspecified, which is the main remaining gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so there is nothing for the description to disambiguate; the baseline applies. The description correctly presents this as an unfiltered national-and-state summary.

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?

The description names a specific dataset (the Big Mac index) and enumerates exactly what it contains: national median price, range and extremes, and median by state versus the national figure. It is immediately clear what the tool returns, though it never explicitly distinguishes itself from siblings such as get_state_prices, which likely overlaps with the per-state portion.

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?

There is no explicit when-to-use or when-not-to-use guidance and no sibling alternative is named. Usage is only implied by the described content scope — an agent must infer that this is the summary/index view rather than a per-item or per-state lookup.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources