Skip to main content
Glama

get_chain_overview

Every chain Fast Food Index prices (10 US chains): flagship item, its national median price and range, and restaurants priced. Data collected weekly from the chains' own ordering systems.

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_chain_overview"
  }
}

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, the description carries the burden and does disclose meaningful behavior: coverage (10 US chains), data provenance (collected weekly from the chains' own ordering systems), and what each record contains. It does not explicitly state read-only status or whether results are ordered, but the nature of the tool makes the safety profile obvious.

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?

Two sentences, no filler, with the scope and returned fields front-loaded. The opening phrase 'Every chain Fast Food Index prices' is slightly awkward grammatically but still parses on first read.

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?

There is no output schema, so the description must convey the return shape, and it does: flagship item, median price, price range, and restaurant count per chain. It stops short of describing ordering or freshness granularity beyond 'weekly', which is a minor gap for a zero-parameter read tool.

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 zero parameters, so there is no parameter meaning to add; the baseline applies. The description correctly implies no filtering is possible, which is itself useful signal.

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 the resource precisely (Fast Food Index prices for 10 US chains) and enumerates the returned fields: flagship item, national median price, range, and restaurant count. It is clearly the broad overview versus a per-item lookup like get_item_price, though it never says so 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: the word 'Every chain' and 'overview' in the name suggest a whole-market snapshot, leaving the agent to infer that get_item_price or get_state_prices handle narrower queries. No explicit when-to-use or when-not-to-use statement, and no sibling is named.

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