Skip to main content
Glama

read_page

Read-only

Retrieve a single LeafWiki page's Markdown content, tags, properties, authors, and current version so you can review it before a version-checked edit.

Instructions

One page: Markdown content, tags, properties, authors and the version needed to change it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "page": "<page>"
    },
    "name": "read_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYesPage id or path
contentNofalse omits the content

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. Beyond that, the description discloses the return payload composition and, usefully, that the version field is a concurrency token required for subsequent edits — meaningful behavioral context not present in the annotations.

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 terse sentence that front-loads the scope ('One page') and then lists the returned data, with zero filler. 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?

With no output schema, the description carries the burden of describing return values and does so explicitly. For a simple two-parameter read it is nearly complete, though it is silent on error cases such as a nonexistent page or path.

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 description coverage is 100%, so both parameters (page id/path and the content toggle) are already documented in the schema. The description adds no syntax, format, or edge-case detail beyond that baseline, so a 3 is appropriate.

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 states the resource precisely (a single page) and enumerates what it returns — Markdown content, tags, properties, authors, version — which distinguishes it from list-style siblings like read_pages_by_tags or read_search. The verb is implicit rather than stated, so an agent infers retrieval from the name plus the noun list, but the scope is unambiguous.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not guidance, and no sibling is named as an alternative. The only usage cue is the indirect hint that the returned version is 'needed to change it', which points toward write_update_page without saying so.

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