Skip to main content
Glama

wanderlog_read

Reads the current Wanderlog page's text and numbered buttons, links, and fields so agents can inspect trip content and choose elements to act on. Optionally limit reading to one element.

Instructions

Read the current Wanderlog page: its text and numbered buttons, links and fields.

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

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.7/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 behavioral burden. It does disclose the return shape (text plus numbered buttons, links, fields), which usefully implies that button numbering is what wanderlog_click consumes. However, it says nothing about behavior when no page is open, whether the call has side effects, or any size/truncation limits.

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?

A single front-loaded sentence with no filler: verb, target, and the exact contents returned. Nothing could be removed without losing information.

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 one-optional-param read tool with no output schema and no annotations, the description covers the essentials, including what the response contains. The main residual gap is the unstated relationship between numbered buttons and the click tool, plus behavior when no page is loaded.

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% and there is only one optional parameter (element), whose description already explains scoping. With zero required params and full schema documentation, the baseline applies; the description neither repeats nor enriches the parameter, so it neither helps nor hurts.

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 description names a specific verb (read) and a specific resource (the current Wanderlog page), and it enumerates the returned content types: text, numbered buttons, links, fields. That distinguishes it from the mutating siblings (click, type, open, close) without needing their schemas. It falls short of 5 only because it never explicitly states the contrast with siblings such as wanderlog_status.

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 implied rather than stated: 'current page' suggests this is called after wanderlog_open and before wanderlog_click, but the description never says when to prefer this over wanderlog_status or wanderlog_guide. There are no exclusions or prerequisites, so an agent must infer the workflow from sibling names.

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