Skip to main content
Glama

Dishes of London

Read one page

get_page
Read-onlyIdempotent

The full text of one page on Dishes of London (https://dishesof.com) as Markdown, with its title, URL, last-updated date and any structured fields (verdicts, categories and so on). Pass the page URL or its path, as returned by search_site or list_pages. Read-only.

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": {
      "url": "<url>"
    },
    "name": "get_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesFull URL (https://dishesof.com/…) or path ("/about/").

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 declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context by specifying the return payload (Markdown plus metadata and structured fields), which matters because there is no output schema. It omits error/not-found behavior, keeping it at 4.

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?

Two tightly written sentences lead with what the tool returns, then how to supply the identifier. The trailing 'Read-only.' duplicates the readOnlyHint annotation and earns little, a small but real redundancy.

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

Completeness5/5

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

With one required parameter, full schema coverage, and no output schema, the description carries exactly the burden it must: it documents the returned content shape and the accepted identifier forms. Nothing an agent needs in order to call this correctly is missing.

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?

There is a single parameter with 100% schema description coverage, so the accepted forms (full URL or path) are already documented in the schema. The description only adds provenance ('as returned by search_site or list_pages'), which is minor added meaning over the schema, matching the baseline 3.

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 specific verb and resource ('The full text of one page') and enumerates exactly what comes back: Markdown body, title, URL, last-updated date, and structured fields. It also implicitly separates itself from the listing/search siblings by telling the agent the URL comes from search_site or list_pages.

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 gives clear usage context: call this after obtaining a URL from search_site or list_pages, which routes the agent correctly among siblings. It stops short of an explicit when-not or a statement of what to do if the page doesn't exist, so it falls short of a 5.

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