Skip to main content
Glama

Search doctor jobs in Germany

search_doctor_jobs
Read-onlyIdempotent

Search Klaro's open jobs for physicians in German hospitals, practices and MVZ (about 12,000, from the employers' own career pages, re-checked several times a day). Returns up to 20 jobs with title, employer, place, specialty, career level and a link to the Klaro job page, plus the total number of matches. Values are German (e.g. specialty "Innere Medizin", state "Bayern", career_level "Assistenzarzt"). Call list_medical_specialties for the exact spellings.

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": "search_doctor_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoTown or postcode, e.g. "Leipzig" or "04103". suggest_job_locations helps with spelling.
sortNorelevance (default) or date (newest first).
textNoFree text in the job title or advert, e.g. "Notaufnahme" or "Weiterbildung Kardiologie".
stateNoBundesland, e.g. "Berlin", "Nordrhein-Westfalen". One value, or up to 5 (any of them matches). Spell values as list_medical_specialties returns them.
contractNoVollzeit (full time), Teilzeit (part time), Befristung (fixed term).
employerNoEmployer name exactly as list_medical_specialties returns it. One value, or up to 5 (any of them matches). Spell values as list_medical_specialties returns them.
specialtyNoFachrichtung, e.g. "Innere Medizin", "Anästhesiologie", "Psychiatrie". One value, or up to 5 (any of them matches). Spell values as list_medical_specialties returns them.
career_levelNoAssistenzarzt, Facharzt, Oberarzt, Leitender Oberarzt or Chefarzt. One value, or up to 5 (any of them matches). Spell values as list_medical_specialties returns them.
hospital_typeNoe.g. "Uniklinik", "Maximalversorger", "MVZ", "Rehaklinik". One value, or up to 5 (any of them matches). Spell values as list_medical_specialties returns them.
posted_withinNoOnly jobs posted in the last 24 hours, 7 days or 30 days.
training_onlyNoOnly jobs at a hospital with a specialty training authorisation (Weiterbildungsbefugnis) in the job's specialty.
instant_apply_onlyNoOnly jobs a doctor can apply to directly through Klaro ("Sofort bewerben").
berufserlaubnis_onlyNoOnly jobs open to doctors who hold a Berufserlaubnis (temporary licence) rather than the full Approbation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, so the safety profile is covered. The description adds genuinely useful behavior beyond them: result cap of 20, the fields returned, the total match count, data freshness (re-checked several times a day) and that values are German. It leaves open what happens when matches exceed 20, since no paging parameter exists.

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?

Front-loaded with the core action and corpus, then return shape, then the spelling hint. Dense and mostly waste-free, though the parenthetical about source pages and re-check frequency is slightly heavier than necessary for the opening sentence.

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?

With 13 optional filters, no output schema and no annotations on result shape, the description properly explains what comes back (title, employer, place, specialty, career level, link, total matches). The remaining gap is whether results are capped at 20 with no way to page, which an agent would want to know before deciding to narrow filters.

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%, so the schema already documents all 13 parameters, their examples, enum values and the 5-value array matching rule. The description's contribution here (values are German, with specialty/state/career_level examples) largely duplicates what the schema already says, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb plus resource plus scope: searches Klaro's physician job listings in German hospitals, practices and MVZ. It states the corpus (~12,000 listings, sourced from employers' own career pages), which distinguishes it from generic `search` and from `compare_jobs`/`get_job_details` without needing to see their schemas.

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?

Gives clear operational context and routing hints to helpers: 'Call list_medical_specialties for the exact spellings' and the city param points at suggest_job_locations. It does not explicitly state when to use this versus the sibling `search` or when to escalate to get_job_details, so it stops short of full when/when-not coverage.

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