Skip to main content
Glama

Read page

wiki_read
Read-only

Read a page's title, content, metadata, and revision, now or at a change or time. Records are read with wiki_records and wiki_get.

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": {
      "path": "<path>",
      "org": "<org>"
    },
    "name": "wiki_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNoRead as of this ISO-8601 time.
orgYesslug of the organization whose wiki to use. Required on every call, even when only one organization is listed; a path never names it.
pathYesThe wiki's name, a colon, then the page's dot-separated path (general:docs.deploy).
changeIdNoRead as of this change.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, closed-world, so safety is covered; the description adds real value by disclosing the returned fields and that historical/point-in-time reads are supported. It does not cover behavior when a requested revision does not exist, but the extra context is meaningful beyond 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?

Two short sentences, front-loaded with the verb and returned fields, followed by the disambiguation clause. Every phrase carries information and nothing is padded.

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 four parameters at full schema coverage and annotations carrying the safety profile, the description is nearly sufficient; listing return fields compensates for the missing output schema. The remaining gap is unspecified interaction between at and changeId.

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 the schema already explains path format, org, at, and changeId in detail. The description only restates the temporal options ('at a change or time') and adds no format, precedence, or mutual-exclusivity guidance for at vs changeId; baseline 3 applies.

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 (Read) and resource (a page) and enumerates exactly what comes back: title, content, metadata, revision. It also scopes the temporal dimension ('now or at a change or time') and names the siblings that handle records, so an agent can separate wiki_read from wiki_get/wiki_records without opening a schema.

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?

The second sentence routes record lookups to wiki_records and wiki_get, implying wiki_read is the page-level reader, and 'now or at a change or time' signals when to supply at/changeId. It stops short of stating what to do when both temporal parameters are supplied, or explicitly saying 'do not use this for records'.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources