Skip to main content
Glama

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

list_news

Read-onlyIdempotent

List published news 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_news"
  }
}

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds two useful behavioral facts: results are limited to published items and each record carries a slug. It says nothing about ordering, total counts, or how pagination terminates.

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, with the resource scope front-loaded and the follow-up action second. Nothing could be removed without losing information.

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, annotated, fully-described two-parameter list tool with no output schema, the description covers what it returns at a high level (published news plus slug) and how to continue. Ordering and result-set size are the only real omissions, and they are minor here.

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 clear descriptions and min/max bounds for limit and offset, so the schema carries the parameter burden and baseline 3 applies. The description adds no meaning beyond it, such as ordering of results or max retrievable records.

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?

"List published news from Alfa-Clinic" gives a specific verb (list) plus resource (news) and adds a scope qualifier (published only), which cleanly separates it from the detail-retrieval siblings. It never names get_news explicitly, so the distinction is inferred from the slug workflow rather than stated.

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?

"Use the returned slug to retrieve details" implies a two-step list-then-fetch workflow and points at the detail tool without naming it. There is no explicit when-to-use versus list_articles/search guidance and no exclusions, so usage is implied rather than prescribed.

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