Fish and chips

Get chip shop details

get_chippy

Read-onlyIdempotent

Get details for one fish and chip shop found by find_fish_and_chips: opening hours, phone, prices visitors reported, recent reviews, and its price compared with the national average. If the shop has a note, mention it to the user.

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": {
      "id": "<id>"
    },
    "name": "get_chippy"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	The shop's id, or its chippynear.me link, from find_fish_and_chips.

Output Schema

Name	Required	Description
`id`	Yes
`link`	Yes
`name`	Yes
`note`	Yes
`town`	Yes
`phone`	Yes
`votes`	Yes
`rating`	Yes
`address`	Yes
`country`	Yes
`openNow`	Yes	"open", "closed" (closed right now), "unknown", or "permanently closed".
`remarks`	Yes	Notes about missing data, e.g. unknown hours or no reviews yet.
`reviews`	Yes	Up to 5 recent reviews, newest first, one per reviewer.
`verified`	Yes
`menuPrices`	Yes	Items visitors reported with a price, most recent first (at most 10).
`openingHours`	Yes	Opening hours grouped by days; null when unknown.
`permanentlyClosed`	Yes	True when the shop has shut down for good.
`nationalComparison`	Yes	The shop's latest reported price compared with the national blended average for its country.
`latestReportedPrice`	Yes	The most recent price a visitor reported for this shop (any item, any size).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful context beyond that: the exact data surfaces returned and a required behaviour for the optional 'note' field, which an agent would not infer from the annotations. It stops short of describing failure modes (unknown/stale id) or data freshness for prices and reviews.

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, both earning their place: the first front-loads purpose plus the full data inventory, the second is a short output-handling rule. No repetition of the title and no filler.

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 single-parameter read tool with an output schema and full annotation coverage, the description covers what is fetched and how to present the notable field. The remaining gap is minor — no guidance on what happens when the id resolves to nothing, which matters for a tool whose id may be a free-text link.

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% and the single 'id' parameter is already documented as accepting either the shop id or a chippynear.me link. The description adds no further meaning, such as how a link is parsed or whether ids are stable — it only restates the provenance. Baseline 3 applies when the schema carries the parameter semantics.

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?

States a specific verb (get) and resource (details for one fish and chip shop) and enumerates the returned content: opening hours, phone, visitor-reported prices, recent reviews, and price vs national average. It also ties the input to the sibling that produces it (find_fish_and_chips), so an agent can distinguish this from the search tool without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The prerequisite is clear: the id must come from find_fish_and_chips, which implicitly establishes use-after-search ordering against the only sibling. It also gives a concrete downstream instruction ('If the shop has a note, mention it to the user'). What is missing is any explicit when-not guidance, such as what to do if the shop is not found or if the user only wants a list.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Fish and chips tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?