Skip to main content
Glama

List wikis

wiki_list
Read-only

List the wikis the caller may see in every organization: each one's organization and name (the start of its paths), what it is for, who reads it, and the caller's capabilities. Call with sections for each wiki's top-level pages.

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

Input Schema

NameRequiredDescriptionDefault
sectionsNoInclude each wiki's top-level pages.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: results are permission-filtered to what the caller may see, and each entry includes the caller's own capabilities. It says nothing about result volume, pagination, or ordering across many organizations, which matters for a cross-org listing.

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?

Two sentences with the core scope front-loaded and no filler. The second sentence is slightly clipped ("Call with sections for each wiki's top-level pages") rather than a clean conditional statement, which costs a bit of clarity but not length.

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, it correctly compensates by enumerating the returned fields, and it explains the single optional flag. For a cross-organization listing tool it could still mention result size or pagination behavior, but nothing an agent needs to invoke it correctly is missing.

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 100% and there is only one boolean parameter, so the baseline is 3. The description's "Call with sections for each wiki's top-level pages" essentially restates the schema's "Include each wiki's top-level pages" without adding depth (e.g., cost of enabling it or what a top-level page list looks like).

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?

The description opens with a specific verb+resource ("List the wikis") and scopes it precisely: everything the caller may see, across every organization. It then enumerates what each entry carries (organization, name/path prefix, purpose, readers, caller capabilities), which implicitly but clearly separates it from single-wiki tools like wiki_get or wiki_search.

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?

It gives useful context (caller-visible wikis, all organizations) and a conditional usage hint for the sections flag, so the agent knows when to enable that option. However, it never states when to reach for an alternative such as wiki_get or wiki_search, nor any prerequisites, leaving sibling routing to inference.

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