Skip to main content
Glama

Yondry: Day Out Planner

by io.github.yondry-ltd

Suggest alternative stops for a plan

suggest_swaps
Read-only

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reasonNo
plan_idYes
stop_indexYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Goes beyond readOnlyHint by clarifying that alternatives are pre-identified, reason parameter is accepted but ineffective, and the tool only works for anonymous plans. No side effects or destructive actions disclosed, but alignment with readOnlyHint is adequate.

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 dense but well-structured: starts with usage, then behavior, then limitation. Could be slightly more concise, but each sentence adds value and is front-loaded with actionable guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Missing output format details—the description doesn't specify what the returned alternatives look like (e.g., object structure, fields). Given no output schema, the tool would benefit from describing the return value.

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?

Despite 0% schema coverage, the description explains plan_id (identifies plan), stop_index (0-based position), and reason (context but unused). This provides necessary meaning beyond the schema's bare names and types.

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?

The description clearly states the tool suggests alternative stops for a plan, using a specific verb 'suggest' and resource 'stops in a plan'. It distinguishes from siblings by specifying it's for swapping stops, not for initial planning or guides.

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 states when to use: for changing/replacing a stop, and instructs to call plan_day first if no plan exists. Implicitly excludes fresh searches by noting alternatives are pre-identified backups. Could be clearer on specific exclusions.

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

All Yondry: Day Out Planner toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
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.

Resources