Skip to main content
Glama

Dishes of London

Search Dishes of London

search_site
Read-onlyIdempotent

Keyword search over every published page on Dishes of London (https://dishesof.com): titles, descriptions, headings and full text. Returns up to 10 pages (max 25) with URL, last-updated date, a one-line description and a snippet around the match. Read-only; cite the page URL. Use get_page for a page's full text.

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

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 10.
queryYesWords to look for, e.g. "bottomless brunch" or "how menus are checked".
sectionNoOptional: limit to one section (pages, home, london).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world safety, so the bar is lower. The description still adds real information the annotations cannot: the result ceiling (10 by default, 25 max) and the exact fields returned (URL, last-updated date, one-line description, snippet), plus the instruction to cite the page URL. It omits matching behaviour such as whether the query is fuzzy or exact and how results are ranked.

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?

Three short sentences, front-loaded with scope and searchable fields, then return shape, then the alternative tool. Every sentence carries information an agent needs and nothing is repeated from structured fields.

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?

With no output schema, the description usefully describes what comes back, which is the main gap it needed to close. It leaves one loose end: there is no offset or cursor parameter, and the description does not say how an agent should handle the case where more than the returned page count exists.

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%, so the baseline is 3. The description only adds that the query matches titles, descriptions, headings and body text; it says nothing extra about the section parameter or what to do when the result cap is hit, so it does not meaningfully outperform the schema.

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 gives a specific verb and scope: 'keyword search over every published page ... titles, descriptions, headings and full text.' It also names the sibling it is not (get_page) so an agent can distinguish the two 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?

It explicitly routes the agent: search here for keywords, then use get_page for a page's full text, and cite the URL. That is clear when-to-use context, but it gives no exclusion against browsing-style tools or any statement about when searching is the wrong choice.

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