Skip to main content
Glama

Paws of London

One place in full

get_place
Read-onlyIdempotent

Everything Paws of London lists for one place: address, website, types, dog policy with how it was checked and any restrictions, every recorded amenity, opening hours, whether it is open now (London time) and nearby stations. Pass the place URL or its id from find_dog_friendly_places. 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": {
      "place": "<place>"
    },
    "name": "get_place"
  }
}

Input Schema

NameRequiredDescriptionDefault
placeYesThe place URL (https://pawsof.london/venue/<id>/...) or its id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/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 behavior, so the trailing 'Read-only' is redundant. The description does add genuine behavioral context beyond annotations: the open/closed computation is timezone-dependent ('London time'), and the dog policy is returned along with how it was checked, telling the agent results include provenance and derived state.

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?

One dense but well-ordered sentence that front-loads what the tool returns, followed by a short usage instruction. The field enumeration is informative rather than padding, though the closing 'Read-only.' duplicates the readOnlyHint annotation and could be dropped.

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 carries the burden of describing results and does so thoroughly, covering derived fields (open now, nearby stations) and policy provenance. Minor gaps remain around error behavior for an invalid id or URL, but nothing essential for correct invocation is missing.

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?

Schema coverage is 100% and the single parameter is already documented as accepting a URL or id. The description adds the meaningful provenance detail that the id comes from find_dog_friendly_places, which is not in the schema, so it earns slightly above the high-coverage baseline.

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 retrieval verb and resource ('Everything Paws of London lists for one place') and then enumerates the exact payload: address, website, types, dog policy with verification method, amenities, hours, open-now status, nearby stations. An agent can distinguish this from the search sibling without opening the 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?

Explicitly routes the agent to the input source: 'Pass the place URL or its id from find_dog_friendly_places,' establishing the intended workflow after a search. It does not state when-not to use it (e.g., bulk lookups), but the single-place granularity is implied by the name and description.

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