Skip to main content
Glama

List pages

list_pages
Read-onlyIdempotent

The published company pages (about, FAQ, contact, terms and the like): slug, title, excerpt, url. Call get_page with the slug for the text.

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
langNoLanguage of the answer: en, de or sr. Default en.en

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, so the safety profile is fully covered and the bar is lower. The description adds useful scope context — only *published* pages, and the exact fields returned — which substitutes for a missing output schema. It does not discuss pagination, ordering, or result size limits, which matters for a list operation.

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?

Two sentences, zero filler. The resource and return fields come first, and the follow-up action is front-loaded rather than buried. Every clause earns its place.

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, listing the returned fields and the 'published only' constraint is exactly the information an agent needs to call this correctly. The only omission is behavior of the `lang` parameter, which the schema already documents adequately.

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?

There is a single optional `lang` parameter with 100% schema description coverage and an enum, so the schema carries the meaning. The description never mentions language selection, adding nothing beyond the schema. Baseline 3 is appropriate under high coverage.

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 identifies the resource precisely — published company pages (about, FAQ, contact, terms) — and enumerates the returned fields (slug, title, excerpt, url). It reads as a noun phrase rather than an explicit 'list' verb, but the resource scope is unambiguous enough to separate it from list_blog_posts, list_events, and other siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It gives a concrete routing rule: fetch this list for slugs and excerpts, then 'Call get_page with the slug for the text.' That names the alternative and the condition selecting it. It stops short of stating when-not-to-use (e.g., that unpublished/draft pages are excluded from results), so it is clear context rather than full when/when-not guidance.

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