Skip to main content
Glama

get_state_prices

One US state: its fast-food price index position (percent vs the national basket) and the flagship item medians in that state (Big Mac, Whopper, Chick-fil-A Chicken Sandwich, Crunchwrap Supreme where priced). Accepts a state name or abbreviation.

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": {
      "state": "<state>"
    },
    "name": "get_state_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYesState name or 2-letter abbreviation, e.g. "Texas" or "TX".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral weight; it does disclose the meaningful caveat 'where priced', warning that not all four items are guaranteed per state. However it says nothing about read-only/safe behavior (only inferable from the 'get' name), how unknown states are handled, currency or units, or ordering of results.

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?

One sentence, front-loaded with scope ('One US state') before the payload detail. The parenthetical item list is dense but each element earns its place by telling the agent exactly which medians to expect. Slightly long on enumeration, short on action wording.

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 one-parameter read tool with no output schema, the description covers the return contents and the conditional availability of items, which is the main thing an agent needs. Only edge-case behavior for invalid or unpriced states is omitted, a minor gap.

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?

The single parameter has 100% schema coverage, and the schema already documents 'State name or 2-letter abbreviation' with examples. The description's 'Accepts a state name or abbreviation' merely restates that, adding no new meaning; baseline 3 applies.

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 resource (one US state) and enumerates exactly what comes back: the fast-food price index position as a percent vs. the national basket, plus flagship item medians (Big Mac, Whopper, Chick-fil-A Chicken Sandwich, Crunchwrap Supreme). That is clear enough to distinguish it from get_big_mac_index or get_item_price without opening a schema, though it describes output rather than stating the retrieval action explicitly.

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 only implied: 'One US state' signals a single-state snapshot rather than a chain- or item-level query, which weakly separates it from siblings like get_chain_overview and get_item_price. There is no explicit when-to-use or when-not-to-use statement, and no guidance on what to do if a state has no pricing data.

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