Skip to main content
Glama

wanderlog_open

Open a Wanderlog page in a signed-in cloud browser to plan trips and manage itineraries. Use it to start or resume trip planning sessions.

Instructions

Open a Wanderlog page in your signed-in Cloud Browser (default https://wanderlog.com) to work with trip planning and itineraries.

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_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://wanderlog.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It does add genuinely useful context by saying the browser is 'signed-in', which implies an authenticated session, and it supplies a default target. It does not disclose what happens on an invalid URL, whether a new tab/session is created, whether an existing page is navigated away from, or what the tool returns.

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?

A single front-loaded sentence with the action and target first, then the default and purpose. The trailing 'to work with trip planning and itineraries' is mildly redundant but does orient the agent to the domain.

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?

The tool is simple with one fully documented optional parameter, so it is nearly complete. However, with no annotations and no output schema, the description should say something about the resulting browser state or return value, and it does not.

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 single url parameter already documents the default https://wanderlog.com, so the description's mention of the default is redundant with structured data. It adds no format or constraint guidance (relative vs absolute URLs, allowed domains).

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?

States a specific verb and resource: open a Wanderlog page in the signed-in Cloud Browser, with the default URL named. This is distinguishable in intent from read/click/type siblings, though the description never explicitly contrasts itself with them.

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

Usage Guidelines3/5

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

Usage is only implied via the clause 'to work with trip planning and itineraries' — an agent can infer this is the navigation entry point before wanderlog_read or wanderlog_click. There is no explicit when-to-use rule, no precondition (e.g. does a session need to exist), and no stated alternative for navigating to an already-open page.

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