Skip to main content
Glama

List docs pages

list_doc_pages
Read-only

Retrieve all Casama documentation pages with their titles and URLs so you can find the right docs or API reference.

Instructions

Every page on docs.casama.ai with its title and address.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that the operation returns every page plus title and address, which is useful, but says nothing about ordering, volume, or whether results are paginated for a site-wide listing.

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 fragment carries the scope and the return shape with zero wasted words, front-loading 'Every page on docs.casama.ai' before the field list.

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?

For a zero-parameter read tool with annotations covering safety, the description supplies the domain and the returned attributes, which is most of what an agent needs. Missing only secondary details such as result size or ordering, and the lack of an output schema makes that omission minor.

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?

The tool takes zero parameters, which is the baseline-4 case, but the description does not clarify that no filtering (by section, product, or query) is possible — a meaningful constraint for a site-wide listing. The schema is empty and fully described, so nothing is missing, yet the absence of filtering is only implicitly conveyed.

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 (every page on docs.casama.ai) and the returned fields (title and address), which implicitly distinguishes an unfiltered full enumeration from siblings like search_docs and read_doc. It lacks an explicit verb such as 'list', leaving the operation type to be inferred from the tool name.

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?

There is no when-to-use guidance, no statement of what this tool should not be used for, and no named alternative among search_docs or read_doc. The phrase 'Every page' hints at full enumeration, but the agent must infer when this beats a search.

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