Skip to main content
Glama

Show page tree

wiki_tree
Read-only

Read the page hierarchy under a path, including record counts.

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

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 path; the name and colon alone (general:) is the whole wiki.
depthNo
changeIdNoRead as of this change.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds that results are hierarchical and include record counts, but says nothing about pagination, size limits, or what happens when the path does not exist.

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 short sentence with zero filler, and the key scope ('under a path') plus the notable output detail ('including record counts') are front-loaded. It is efficient if thin.

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 takes five parameters with time-travel and depth options and has no output schema, so the description should carry more. Mentioning record counts helps, but the depth parameter's effect and the return shape are left unexplained.

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 80%, so the schema mostly carries the load — org, path, at, and changeId all have descriptions. The description reinforces the path-as-scope semantics but adds no meaning for depth (undocumented in the schema, default 1, capped at 3) or for the at/changeId time-travel pair.

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 concrete verb and resource — reading the page hierarchy beneath a path — and adds that record counts are included. That is specific enough to separate it from flat-list or single-page readers like wiki_list/wiki_get, though it never names 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 Guidelines2/5

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

The word 'path' implies a scoping model but the description gives no when-to-use guidance, no exclusions, and no pointer to alternatives for flat listing, searching, or fetching a single page. An agent must infer the boundary itself.

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