Skip to main content
Glama

Klaro – Arztstellen in Deutschland

Suggest job locations

suggest_job_locations
Read-onlyIdempotent

Towns with open doctor jobs that match a few letters or a postcode, with their Bundesland. Use the result as search_doctor_jobs' city.

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": {
      "query": "<query>"
    },
    "name": "suggest_job_locations"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesStart of a town name or a postcode.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 the safety profile is covered. The description adds a genuinely non-obvious behavioral constraint: results are limited to towns that currently have open doctor jobs, which explains why a valid town may be absent. It does not address result caps, ordering of suggestions, or empty-result behavior.

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 with zero filler: the first states what is returned and under what filter, the second states the downstream use. Information is front-loaded and every clause earns its place.

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, annotation-covered, no-output-schema tool, the description covers return content (town plus Bundesland), matching rule, and next step. Minor gaps remain around result limits and behavior on zero matches, but nothing essential to calling it correctly 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 coverage is 100% and the schema already describes the single 'query' parameter as the start of a town name or a postcode. The description restates this as 'a few letters or a postcode' without adding prefix-matching semantics, case sensitivity, or postcode format detail beyond the schema. Baseline 3 applies when the schema carries the parameter documentation.

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 specifies the resource (towns with open doctor jobs) and the matching semantics (a few letters or a postcode), plus an extra return field (Bundesland). It distinguishes itself from siblings by naming search_doctor_jobs as the downstream consumer, though the operative verb is only implied by the noun phrase rather than stated outright.

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?

'Use the result as search_doctor_jobs' city' gives an explicit, actionable when-to-use rule, tying this autocomplete-style lookup to the job search tool. It stops short of stating when not to use it (e.g. when a full known city name is already available) or what to do when no towns match.

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