Skip to main content
Glama

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

get_disease

Read-onlyIdempotent

Get a published disease by slug, including its public text and canonical URL.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_disease"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the bar is lower. The description adds real behavioral detail beyond them: only *published* diseases are retrievable, and the response carries the public text and canonical URL. Still missing is what happens for an unknown or unpublished slug (error vs empty result).

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?

A single front-loaded sentence with no filler; the selector ('by slug') and the returned fields are stated up front.

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 one-parameter read tool with full annotations and no output schema, this is nearly complete: it says what is fetched and what comes back, compensating for the absent output schema. The one omission is the not-found/unpublished behavior, which matters for an agent handling misses.

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 parameter with 0% schema description coverage, so the description must carry the meaning. It establishes that slug is the record identifier for a disease and that only published records resolve, but adds nothing about slug format, casing, or where to source it, leaving a real gap for the sole required input.

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 gives a specific verb ('Get') and resource ('a published disease') plus the lookup key ('by slug'), and it names the payload ('public text and canonical URL'). The 'disease' resource plus the 'published' qualifier separates it from the sibling list_diseases/other get_* tools, though no sibling is named explicitly.

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?

Usage is implied rather than stated: an agent can infer this is the single-record lookup to use once a slug is known, and that list_diseases/search would be the way to obtain one. There is no explicit when-to-use/when-not guidance or mention of alternatives, so it stops at the minimum-viable bar.

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