Skip to main content
Glama
Sign In

UK Places MCP

by io.github.donniertf-hub
OverviewDiscussionsAdmin

whats_on_discover

Free: what's on near a UK postcode for a date — weather (MET Norway, ~9 days ahead), sunrise/sunset, bank holiday flag (GOV.UK), and the 3 nearest event venues (theatres, cinemas, arts centres, music venues, stadiums, museums; © OpenStreetMap). Live event listings appear when enabled. Geocoded via postcodes.io.

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": {
      "postcode": "<postcode>"
    },
    "name": "whats_on_discover"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoYYYY-MM-DD, 'today' or 'tomorrow' (Europe/London). Default today.
postcodeYesUK postcode or outward code (e.g. M1 1AE / M1)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description does useful work by disclosing data sources, the ~9-day weather horizon, the 3-nearest-venue limit, and that live listings depend on being enabled. It still omits details such as authentication/rate limits, error behavior, and what 'when enabled' concretely means.

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?

The description is front-loaded with the core purpose and then enumerates returned data. It is dense but efficient, with no obvious filler, though the long parenthetical list makes it slightly less scannable.

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 two-parameter discovery tool with no output schema, the description adequately explains what data comes back, its sources, and the weather time horizon. It is not exhaustive about edge cases or response shape, but it is complete enough for an agent to call it correctly.

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 both parameters are already fully documented in the schema. The description adds context about postcode geocoding and the weather date range, but it does not provide meaningfully more parameter-level detail beyond the schema.

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 clearly states a specific verb and resource: it returns what's on near a UK postcode for a date, and it lists the included data types (weather, sunrise/sunset, bank holiday, nearby venues). It is clear enough to distinguish from generic amenity tools, but it does not explicitly contrast itself with the sibling whats_on_pack.

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 by 'Free' and 'near a UK postcode for a date', and the ~9-day weather range gives some context. However, it does not explicitly say when to use this instead of whats_on_pack or other siblings, nor does it state when-not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All UK Places MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources