Skip to main content
Glama

List the pages of the i22 website

i22_ai_page_list
Read-onlyIdempotent

Lists the published pages of the i22 website in one language with title, URL and description. Use it to get an overview; prefer i22_ai_site_search for specific questions.

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

Input Schema

NameRequiredDescriptionDefault
localeNoLanguage of the content: "de" (default) or "en".de

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already declare this is read-only, idempotent, non-destructive, and not open-world. The description adds useful behavioral context: it returns published pages with title, URL, and description in one language. It does not mention pagination, ordering, or result limits, which are minor gaps for a simple list endpoint.

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?

The definition is two concise sentences with no wasted wording. It front-loads the core operation and then immediately provides the routing guidance.

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 simple one-parameter list tool with annotations and no output schema, the description is nearly complete: it states scope, return fields, and when to use it. The only meaningful omission is any statement about pagination or ordering of the returned page list.

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 one optional parameter, locale, and schema coverage is 100%, so the schema already documents the enum and default. The description reinforces the one-language scope but adds no format or semantic detail beyond what the schema provides.

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 states a specific verb and resource: lists published pages of the i22 website. It also clarifies scope (one language) and return contents (title, URL, description), so the agent can distinguish it from search and page-reading tools.

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

Usage Guidelines5/5

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

It explicitly says to use this tool for an overview and to prefer i22_ai_site_search for specific questions. That gives both a use case and a concrete alternative, leaving little ambiguity about tool selection.

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