Skip to main content
Glama

get_price_changes

The latest verified fast-food price changes: gated repricing events (same item, same old and new price, at 40+ restaurants) from the most recent weekly collection round.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many events to return (1–25, default 10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does useful work: it discloses the 40+ restaurant threshold that defines a qualifying event, states the data is 'verified', and bounds freshness to the most recent weekly round (so no historical depth). It does not cover ordering of results or whether the underlying data has gaps, which keeps it short of a 5.

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 tightly packed sentence with the key qualifier ('gated repricing events') front-loaded and its jargon defined inline via parenthetical. It borders on density — the criteria and the freshness scope compete inside a single sentence — but nothing is wasted.

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-only list tool with no output schema and no annotations, the description conveys enough to invoke it correctly: what an event is, how recent it is, and how many to request. The absence of any statement about result ordering or what a returned event record contains is 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?

Schema description coverage is 100%: the single 'limit' parameter already documents its 1–25 bounds and default of 10. The description adds nothing about parameter behavior, so the baseline of 3 applies.

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 names a precise resource: verified fast-food repricing events, defined concretely as 'same item, same old and new price, at 40+ restaurants,' scoped to the latest weekly collection round. That level of specificity separates it from item-level siblings such as get_item_price or get_state_prices without having to name them.

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 rather than stated: the 'latest ... most recent weekly collection round' phrasing signals this is for current repricing signals, not historical analysis or individual item lookups. However, no alternative tool is named and no exclusion condition is given, so the agent must infer when to prefer it over siblings.

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