Skip to main content
Glama

get_menu

Fetch menu items and prices taken from the restaurant's own website only. If none are found, returns a note to type items. Does not invent dishes.

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": {
      "locality": "<locality>"
    },
    "name": "get_menu"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
localityYes
placeTokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does add real value: it discloses the data source restriction and an anti-fabrication contract, plus an explicit fallback ('returns a note to type items'). It stops short of saying whether this is a live external fetch, how long it takes, or what happens when the locality/name combination matches multiple restaurants.

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?

Three short sentences with the key constraint front-loaded and no filler. The final two sentences are closely related (fallback vs. no-fabrication) but each adds a distinct guarantee, so nothing is truly wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple three-string lookup with no output schema, the description covers provenance, failure mode, and result content (items and prices). What is missing is how the target restaurant is identified from the three parameters — the main thing an agent needs in order to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three parameters, so the description must compensate and does not. It never explains what 'name' (restaurant name?), 'locality', or 'placeToken' mean, nor how placeToken differs from name/locality, leaving an agent to guess at a required field.

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?

Specific verb and resource: 'Fetch menu items and prices' with an explicit sourcing constraint ('from the restaurant's own website only'). It is clearly distinct from siblings like place_order or order_status by being a read of menu data, though it never names a sibling for contrast.

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: an agent can infer this is the pre-order lookup step. There is no explicit guidance about when to call this versus search_restaurant (to resolve the restaurant first) or quote_order, and no stated prerequisites for the required 'locality' parameter.

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