Skip to main content
Glama

Dishes of London

List pages

list_pages
Read-onlyIdempotent

Every published page on Dishes of London (https://dishesof.com), newest first, with URL, section, last-updated date and description. 2154 pages in total; filter by section and page through with offset.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 50.
offsetNoDefault 0.
sectionNoOptional: pages, home, london.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 contributes real extra context beyond that: a fixed corpus size (2154 pages), explicit newest-first ordering, and the shape of each record returned — all of which matter for deciding whether to page through the whole set.

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 front-loaded with what matters: scope and ordering first, then corpus size and the filtering/paging mechanism. No filler, no restatement of the title.

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 three-optional-parameter read-only list tool with no output schema, the description covers scope, ordering, returned fields, corpus size and paging — essentially everything needed to call it correctly. The only real gap is routing versus the sibling search/get tools, which is a usage concern rather than a completeness one.

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 limit, offset and section are already documented, including defaults (50/0) and the section values (pages, home, london). The description reinforces the section filter and offset paging and adds the total count needed to reason about paging, but adds no syntax or semantics beyond the schema; 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?

The description names a specific resource and scope: 'Every published page on Dishes of London', with ordering ('newest first') and the returned fields (URL, section, last-updated, description). That is far more concrete than the bare title 'List pages', though it never contrasts itself with siblings like get_page or search_site, so the agent must infer that this is the bulk-listing option.

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 implied operationally ('filter by section and page through with offset'), which tells the agent how to narrow results but not when to prefer this over find_dishes, search_site or get_page. No exclusions or alternative-routing guidance is given, so the choice between listing everything and searching is left to inference.

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