Skip to main content
Glama

list_pages

Retrieve wiki pages, optionally filtered by type, to locate sources, entities, concepts, topics, or answers in the knowledge base.

Instructions

List wiki pages, optionally filtered by type (source, entity, concept, topic, answer).

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

Input Schema

NameRequiredDescriptionDefault
typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. "List" implies a read-only operation, but nothing is said about pagination, result ordering, default result size, or whether all pages are returned at once — gaps that matter for a listing tool with no annotation coverage.

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 front-loaded sentence with the resource first and the filter second; no filler and nothing redundant.

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?

For a one-optional-parameter list tool with no output schema, the description covers the parameter domain well, but it omits any sense of result volume or ordering, which an agent needs to know before calling it on a large wiki.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the schema types "type" only as a plain string with no enum. The description compensates by enumerating the five accepted values (source, entity, concept, topic, answer), which is meaning the schema does not provide and directly prevents invalid input.

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 a specific verb and resource ("List wiki pages") plus the filtering dimension, so the agent knows exactly what the tool returns at a high level. It does not distinguish itself from the sibling search_wiki or read_page, leaving the agent to infer the difference between listing and searching.

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?

"Optionally filtered by type" implies the filter is optional and that unfiltered calls return everything, which is useful implied guidance. However, there is no explicit statement of when to prefer this over search_wiki or recent_activity, and no exclusions or prerequisites are given.

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