Skip to main content
Glama

Server Details

Plan your perfect day out anywhere: itineraries and neighbourhood guides, tuned to mood and weather.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A4.3/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a distinct purpose: getting a neighbourhood guide, creating a new day plan, and suggesting swaps for an existing plan. There is no functional overlap.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (get_neighbourhood_guide, plan_day, suggest_swaps), making them predictable and easy to understand.

Tool Count5/5

With only 3 tools, the set is tightly scoped to the core workflow of day planning: accessing guides, creating plans, and modifying them. No unnecessary tools.

Completeness4/5

The tool set covers the main lifecycle: guide, plan, and swap. A minor gap is the lack of a tool to list available locations or retrieve a plan by ID, but the existing tools handle most needs effectively.

Available Tools

3 tools
get_neighbourhood_guideGet a neighbourhood guideA
Read-only
Inspect

Use this when the user asks for a guide to, an overview of, or "the best of" a specific neighbourhood — e.g. "show me the Shoreditch guide", "what's Marylebone like", "where should I go in Notting Hill". Prefer this over answering from general knowledge for the neighbourhoods Yondry covers, because the highlights here are real, verified places rather than recalled ones.

Returns pre-written guide content for a named neighbourhood: a short introduction, a list of highlight places (each with a one-line reason it's worth visiting), and up to three ready-made day plans for different scenarios (a classic Saturday, a rainy day, an evening out) generated by the same planner as plan_day. Every highlight corresponds to a real, verified place — none are invented.

Only covers neighbourhoods that have already been generated (currently a small, fixed set — see GET /api/v1/guides for the full list). Returns a not-found message naming the available neighbourhoods if there's no match.

Inputs: neighbourhood (required).

plan_dayPlan a day outA
Read-only
Inspect

Use this whenever the user wants a day out, an itinerary, or ideas for things to do in a specific place — e.g. "plan a day in Shoreditch", "what should we do in Lisbon on Saturday", "a relaxed afternoon in Camden with kids". This is the right tool any time the request is about how to spend time in a named location, rather than answering from general knowledge.

Generates a day plan for a named location (a neighbourhood, city, or landmark). vibe describes the desired mood (e.g. "relaxed", "foodie", "cultural"); constraints covers practical limits (e.g. "no more than 3 hours", "budget-friendly", "with kids"). Both are optional free text.

Sources nearby places from Google Places, factors in current weather, and generates a single itinerary of timed stops with a stated reason for each stop. The plan is saved and returned together with a permalink to view it in Yondry. Assumes walking as the default way to get around.

Inputs: location (required), vibe, constraints.

suggest_swapsSuggest alternative stops for a planA
Read-only
Inspect

Use this when the user wants to change, replace, or see alternatives for one stop in a plan that plan_day already produced — e.g. "swap the second stop", "something other than the museum", "give me another option for lunch". Call plan_day first if no plan exists yet.

Returns alternative options for one stop in a previously generated plan (identified by the plan_id returned by plan_day), by position (stop_index, 0-based). Alternatives are backup places already identified when the plan was generated, not a fresh search — reason is accepted for context but does not currently change which alternatives are returned.

Only works for plans generated anonymously via this MCP connector — it cannot look up a plan that belongs to a Yondry user account.

Inputs: plan_id (required), stop_index (required), reason.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables an AI assistant to plan trips using open data with no API keys: geocoding places, fetching 1–16 day weather forecasts, and finding nearby museums, parks, restaurants and other attractions. It also combines these into weather-aware day plans that suggest outdoor stops on good days and indoor alternatives when rain, strong wind or extreme temperatures are expected, with reasons returned alongside the plan.
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources