Skip to main content
Glama

wanderlog_guide

Get guidance on Wanderlog screens and the sign-in link before planning or editing trips. Use it first to locate the right workflow for your trip tasks.

Instructions

How to work in Wanderlog (trip planning and itineraries): its screens and the sign-in link. Call this first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wanderlog_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in Wanderlog, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full load, and it does disclose the two things an agent needs: the content returned (screens plus a sign-in link) and the implication that sign-in is a prerequisite step. It never states that the call is read-only and side-effect free, nor how the guide output relates to later tool calls, so the safety profile is inferred rather than declared.

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?

Two short sentences with no filler; the resource scope comes first and the directive follows. The phrasing is telegraphic to the point of being slightly elliptical ("its screens and the sign-in link"), but nothing is redundant.

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?

For a low-complexity guidance tool with full schema coverage and no output schema, this is adequate: it tells the agent it exists to orient it and to invoke it first. However, because no output schema exists, the description is the only place to explain the shape of the returned guide, and it only gestures at it ("screens and the sign-in link").

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% (the single optional `task` parameter is fully described in the schema), so the baseline is 3. The description adds nothing about how the free-text task shapes the returned guide, and it does not clarify whether the parameter may be omitted.

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 definition names the resource (Wanderlog, a trip planning tool) and the content it exposes: its screens and the sign-in link. That distinguishes it from the action siblings (click, type, read, open) which operate the UI rather than explain it. It stops short of a sharp verb ("provides guidance about"), so purpose is clear but framed as a fragment.

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?

"Call this first" gives an explicit ordering directive and a clear use condition, which is exactly the guidance an agent needs for an orientation tool in front of a UI-automation suite. It does not state when to skip it or name the alternatives, so it falls just short of 5.

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