Skip to main content
Glama

Альфа-Клиник (Alfa-Clinic, Moscow)

list_pages

Read-onlyIdempotent

List published pages from Alfa-Clinic. Use the returned slug to retrieve details.

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
limitNoMaximum records, default 20.
offsetNoPagination offset, default 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds one useful behavioral fact beyond that: only published pages are returned. It does not describe pagination behavior or result ordering, which the schema only partially implies through limit/offset.

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 short sentences with no filler, and the core purpose is front-loaded before the follow-up hint. Nothing in it needs to be trimmed, though it is near the minimum 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?

For a simple two-parameter, read-only list tool with full schema coverage and rich annotations, the description supplies the essentials: source, resource scope, published-only filter, and the natural next step. Only minor gaps remain, such as result ordering and whether a total count is returned, and the absence of an output schema makes those low-stakes.

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 description coverage is 100% and both parameters (limit, offset) carry their own defaults and bounds, so the description is not required to compensate. It adds no meaning beyond the schema, which is appropriate here but earns only the baseline.

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?

States a specific verb and resource ("List published pages from Alfa-Clinic") and names the domain so it is distinguishable from list_articles, list_doctors and other siblings. It stops short of explicitly contrasting itself with the list_* family or with get_page, leaving the boundary to be inferred.

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?

The second sentence, "Use the returned slug to retrieve details," implies the list-then-fetch workflow and points the agent at the detail tool as the follow-up, which is genuine usage context. However, it never states when to prefer this tool over alternatives, what happens if no pages are published, or any preconditions.

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