Skip to main content
Glama

read_tree

Read-only

Retrieve an indented page hierarchy with paths and IDs for the whole wiki or beneath one page, with optional depth limits.

Instructions

Page hierarchy as indented lines with path and id, for the whole wiki or below one page.

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": "read_tree"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthNoLevels shown, default 3; deeper ones are counted
underNoPage id or path to list below; omit for the whole wiki

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?

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), so the description adds the return format—indented lines carrying path and id—which matters because no output schema exists. It stops short of disclosing size/limits behavior: a whole-wiki tree can be large, and while the schema mentions deeper levels are counted, the description says nothing about truncation or output scale.

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 sentence with no filler, front-loading the resource and return format before the scope qualifier. Every clause carries 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 does its main job by describing the return shape, and annotations handle the safety profile while the schema handles both parameters. The only meaningful gap is the absence of any note about output volume for whole-wiki traversal.

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 (depth, under) are already fully documented, including the depth default and counting behavior. The description restates the 'under' scope ('whole wiki or below one page') but adds no new meaning beyond the schema, which matches the baseline 3.

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 the resource (page hierarchy) and the returned shape (indented lines with path and id), plus the two scopes: whole wiki or below one page. That is specific enough to distinguish it from flat readers like read_page or read_search, though it does not explicitly contrast with a sibling.

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: you call it when you want to browse structure, either globally or under a specific page, which is signaled by 'for the whole wiki or below one page.' There is no explicit when-not guidance, no named alternative (e.g., search or property-based listing), and no note on cost of running it over the whole wiki.

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