Skip to main content
Glama

get_item_price

The price of one menu item at one chain: national median, typical range, restaurants priced, and the cheapest / priciest states (for flagship items) or stores. Chain accepts names like "McDonald's", "taco bell", "bk".

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": {
      "chain": "<chain>",
      "item": "<item>"
    },
    "name": "get_item_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYesMenu item name, e.g. "Big Mac" or "Whopper".
chainYesChain name or slug, e.g. "McDonald's" or "taco-bell".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does describe what comes back (median, typical range, sample size, extremes), which is genuine behavioral disclosure, but it never states currency, what happens for an unknown chain or item, or whether the sample size can be zero.

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 no filler: scope first, returned fields second, input convention last. Nothing could be removed without losing information.

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 two-required-parameter read tool with no output schema and no annotations, the description covers purpose, result shape, and input flexibility. Only the currency/units and the empty-result case are left unstated.

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?

Schema coverage is 100%, so the baseline is 3. The description earns an extra point by adding matching behavior not visible in the schema: chains accept names with loose casing and abbreviations ("taco bell", "bk"), which tells the agent it need not normalize input.

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 resource and scope — "the price of one menu item at one chain" — and enumerates the returned figures (median, range, restaurant count, cheapest/priciest states or stores). The singular-item/singular-chain scoping implicitly separates it from broader siblings like get_chain_overview and get_state_prices, but no sibling is named outright.

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 implied by the scope statement: this is the single-item, single-chain lookup. There is no explicit "use X instead when..." routing, no prerequisite or failure guidance, though the parenthetical about flagship items clarifies which geographic breakdown you receive.

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