Skip to main content
Glama

search_items

Search priced menu items by name across all 10 chains (e.g. "nuggets", "frosty", "burrito"). Returns matching items with national medians and restaurant counts.

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": {
      "query": "<query>"
    },
    "name": "search_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoOptional: restrict to one chain (name or slug).
queryYesItem name or fragment to search for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description bears the full burden. It helpfully discloses the return payload (national medians and restaurant counts) and the 10-chain scope, but says nothing about matching semantics (substring, case sensitivity, fuzzy), result caps, or empty-result behavior.

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?

Two sentences, zero filler, with the scope and examples front-loaded before the return description. Every clause earns its place.

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 simple two-parameter read tool with no annotations or output schema, the description covers scope, query intent, and the shape of results. The remaining gap is matching behavior and result limits, which is minor for this complexity.

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 coverage is 100%, so both parameters are already documented in the schema. The description's examples ('nuggets', 'frosty', 'burrito') illustrate fragment-style queries but largely restate the schema's own 'item name or fragment' wording, so 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?

States a specific verb and resource (search priced menu items by name), plus the scope (across all 10 chains) and concrete example queries. It does not explicitly differentiate from siblings like get_item_price, but the 'search by fragment' framing makes the distinction reasonably inferable.

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 ability to search by name fragment and the optional chain restriction suggest this is the discovery tool for when the exact item name is unknown. There is no explicit when-to-use/when-not-to-use statement or pointer to get_item_price for exact lookups.

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