Skip to main content
Glama

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

list_diseases

Read-onlyIdempotent

List published diseases 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_diseases"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum records, default 20.
offsetNoPagination offset, default 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description's one real addition is the 'published' scope, which tells the agent unpublished items are excluded, but it says nothing about ordering, pagination behavior, or result fields.

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 short sentences, zero filler, with the resource and scope stated first and the follow-up hint second. Nothing needs trimming.

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-optional-parameter list endpoint with no output schema, the description covers what it returns at a coarse level and how to continue to details. It could mention what a disease record contains, but nothing critical to correct invocation is missing.

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% with only limit and offset, both fully documented with defaults and bounds in the schema. The description adds no additional meaning about pagination, so the baseline 3 applies.

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 a specific verb and resource ('List published diseases') plus the source system (Alfa-Clinic), which is clearly distinct from siblings like get_disease or search. It doesn't explicitly state how it differs from the other list_* tools, but the resource noun is unambiguous.

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?

It gives a next-step hint ('Use the returned slug to retrieve details'), which implies this is a discovery step preceding detail retrieval, but it never names get_disease or states when to use search instead. Usage is implied rather than directed.

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