Skip to main content
Glama
Sign In
wanderlog-mcp

wanderlog-mcp

by foxnaim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Move a block within its itinerary section

wanderlog_move_block

Move an existing place or reservation block to a new position within the same Wanderlog section without deleting or recreating it, preserving its ID, notes, times, and booking details.

Instructions

Moves an existing place or reservation block to another position within its current Wanderlog section without deleting or recreating it. The original block ID, notes, images, times, booking details, and other metadata are preserved.

Select the block using the same natural-language references as wanderlog_remove_place, including day filters and ordinal prefixes. Choose exactly one destination:

  • position: a 1-based position in the section's complete displayed block order

  • before: another place or reservation block in the same section

  • after: another place or reservation block in the same section

Positions count all displayed blocks, including notes and checklists — but notes and checklists cannot be used as before/after targets, which resolve only to place or reservation blocks. Cross-section moves are not supported; do not emulate them by removing and re-adding the block, which discards its ID, notes, times, and booking details. If a reference is ambiguous, nothing is changed and the tool returns candidates for a more specific retry.

Input Schema

NameRequiredDescriptionDefault
afterNoMove immediately after this naturally referenced place or reservation block in the same section. Notes and checklists are not valid targets.
blockYesNatural-language reference to the place or reservation block to move. Uses the same names, role keywords, day filters, and ordinal prefixes as wanderlog_remove_place.
beforeNoMove immediately before this naturally referenced place or reservation block in the same section. Notes and checklists are not valid targets.
positionNoMove to this 1-based position in the section's complete displayed block order, including notes and checklists.
trip_keyYesThe trip containing the block.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.2

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does well: it promises preservation of ID, notes, images, times and booking details, and specifies that an ambiguous reference changes nothing and returns candidates. It does not state permission/auth requirements or what a successful response contains, leaving a modest gap for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the effect and the preservation guarantee, then a compact bullet block for the three destination modes, then the failure behavior. No sentence is redundant and the structure mirrors how an agent would reason about the call.

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 5-parameter mutation tool with no annotations and no output schema, the description covers effect, constraints, aliasing to a sibling, and error/ambiguity behavior. Only the success response shape and any permission prerequisites are left unstated.

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%, so baseline is 3; the description adds genuinely new meaning by declaring the three destination options mutually exclusive (the schema has no oneOf) and by clarifying that positional counting includes notes/checklists while before/after targets exclude them.

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 (moves an existing place or reservation block) plus the precise scope (another position within its current section) and the key non-behavior (does not delete or recreate). This clearly separates it from wanderlog_add_place and wanderlog_remove_place.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly enumerates the three mutually exclusive destination modes, states that exactly one must be chosen, rules out cross-section moves, and warns against the tempting remove-and-re-add workaround. It also points to wanderlog_remove_place as the shared reference syntax, giving an agent everything needed to pick this tool and call it correctly.

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