Skip to main content
Glama
Sign In
wanderlog-mcp

wanderlog-mcp

by foxnaim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Add a note to a Wanderlog trip

wanderlog_add_note

Add inline text notes to a Wanderlog itinerary day or section for directions, practical tips, food recommendations, and timing guidance, keeping trip stops connected.

Instructions

Adds a text note to a Wanderlog trip. Notes appear inline between places in a day, acting as the connective tissue of the itinerary. Every well-built day should have notes between stops. Supply "day" for a dated itinerary day or "section" for an undated section such as "Notes" or "Food & Drink". When both are provided, "section" takes precedence. Omit both to add to the default "Places to visit" list.

When to add a note (do this after adding each place or group of places):

  • How to get there: "Walk 15 min along the South Bank, or take the Jubilee line one stop"

  • Practical tips: "Book tickets online at least 2 days ahead — sells out in summer"

  • Food/drink recs: "Try the salt beef bagel at Beigel Bake — cash only, open 24hrs"

  • Time guidance: "Budget 2-3 hours here. Open 10am-6pm, closed Tuesdays"

  • Neighborhood context: "This area is great for wandering — no rush, just explore the lanes"

Returns a confirmation of where the note was added.

Input Schema

NameRequiredDescriptionDefault
dayNoOptional day to add the note to. Accepts 'day 2', 'May 4', or ISO '2026-05-04'. If 'section' is also provided, the section takes precedence. Omit both to add to the 'Places to visit' list.
textYesThe note text. Plain text — can be multi-line.
sectionNoOptional undated section to add the note to, identified by its heading (e.g. 'Notes', 'Food & Drink', or 'Places to visit'). Matching is case-insensitive and takes precedence over 'day'. Omit both to add to the 'Places to visit' list.
trip_keyYesThe trip to add the note to. Use wanderlog_list_trips if you don't know the key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.2

TDQS

A4.2/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden: it discloses the destination-resolution precedence ('section' wins over 'day'), the default target list, and that the call returns a confirmation of where the note landed. It omits failure modes (e.g., what happens with an unmatched section name) and any auth or rate-limit context.

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?

Placement rules are front-loaded before the example bullets, and the structure is easy to scan. The five illustrative bullets are somewhat generous in volume but each demonstrates a distinct note type, so they mostly earn their place.

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

Completeness5/5

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

For a four-parameter mutation tool with no output schema, the description covers purpose, placement semantics, timing relative to other tools, and the shape of the return value. An agent has everything needed to invoke 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 coverage is 100% and the per-parameter descriptions already explain day formats, section matching, and precedence. The description's restatement of the day/section/default rule adds little beyond what the schema provides, so the baseline 3 applies.

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 verb and resource ('Adds a text note to a Wanderlog trip') and immediately explains where the note lands in the itinerary, which is what distinguishes it from sibling tools like wanderlog_edit_note and wanderlog_annotate_place.

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?

Gives explicit procedural guidance ('do this after adding each place or group of places') plus concrete content categories with example text, and defines the day/section/default resolution rules. It stops short of naming alternative tools or stating when not to add a note.

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

Deploy Server

Other Tools