Skip to main content
Glama

Klaro – Arztstellen in Deutschland

List medical specialties and filters

list_medical_specialties
Read-onlyIdempotent

The medical specialties (Fachrichtungen) and the other values search_doctor_jobs accepts (Bundesländer, career levels, hospital types, largest employers), each with its number of open jobs right now.

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_medical_specialties"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds real value beyond them by disclosing what the response contains (each filter value paired with a live count of currently open jobs, 'right now'), which signals freshness and payload shape for a tool with no output schema.

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?

A single front-loaded sentence that puts the primary resource first and the parenthetical enumerations second; every clause carries information about content or counts. The nested parenthetical makes it slightly dense, but nothing is redundant.

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 no-parameter, read-only lookup with no output schema, the description covers both what is returned (filter value categories) and the accompanying job counts, which is the key completeness burden here. Minor omissions like ordering of results or whether counts are approximate are not critical for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing to disambiguate and the baseline is 4. The description correctly implies no input is needed by framing the tool as a pure enumeration of accepted filter values.

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 the resource concretely (medical specialties/Fachrichtungen plus Bundesländer, career levels, hospital types, largest employers) and ties it to the sibling search_doctor_jobs, so an agent can tell it is a reference/enumeration lookup, not another job search. It lacks an explicit verb ('List...'), which keeps it just short of a 5.

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

Usage Guidelines4/5

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

By stating these are 'the other values search_doctor_jobs accepts', it makes clear this is the vocabulary/discovery step that precedes a filtered search. There is no explicit 'call this before search_doctor_jobs' directive and no when-not to use it (e.g., when filter values are already known), so it stops at clear context rather than explicit routing.

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