Skip to main content
Glama

Paws of London

What Paws of London covers

list_coverage
Read-onlyIdempotent

How many places Paws of London lists, by type and by London borough and neighbourhood, and the amenity filters find_dog_friendly_places accepts. Read-only.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so 'Read-only' in the description is largely redundant. The genuinely additive content is the disclosure of what data comes back (counts by type/borough/neighbourhood and the valid filter set), but it says nothing about freshness of the counts, whether borough and neighbourhood results are sampled, or the response shape for a no-argument call.

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?

A single sentence with no filler; the enumerable dimensions (type, borough, neighbourhood, amenity filters) are front-loaded and the safety note is a terse trailing clause. Nothing could be cut without losing information.

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 zero-parameter, no-output-schema tool with full annotation coverage, the description supplies the key missing piece: what the returned counts and filter lists actually describe. It stops short of noting whether the result is static reference data or computed live, which is the one thing an agent might still wonder about.

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

Parameters4/5

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

The tool takes zero parameters, so there is no per-parameter semantics for the description to carry; the schema baseline of 4 applies. The description appropriately spends its words on output content instead of inventing input detail.

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 concrete resource: counts of places broken down by type, borough, and neighbourhood, plus the amenity-filter vocabulary used by find_dog_friendly_places. That clearly separates it from the search and detail siblings. It loses a point because it bundles two purposes (coverage statistics and filter enumeration) into one run-on clause without a leading verb, so the primary intent takes a second read.

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?

Mentioning that it exposes the amenity filters find_dog_friendly_places accepts implicitly signals a discovery/browse-before-searching role, and 'Read-only' hints at safe exploratory use. However, the description never states explicitly when to call this versus find_dog_friendly_places or get_place, and gives no exclusions or preconditions.

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