Skip to main content
Glama

Klaro – Arztstellen in Deutschland

Search (research clients)

search
Read-onlyIdempotent

Search Klaro's doctor jobs in Germany for research clients (returns ids, titles and links; read one with fetch). A specialty, career level or Bundesland named in the query is used as a filter, the other words as free text or a town. Prefer search_doctor_jobs for filtered searches.

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

Input Schema

NameRequiredDescriptionDefault
queryYesWhat to look for, e.g. "Kardiologie Hamburg Oberarzt".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive and closed-world, so the safety profile is handled. The description adds genuinely new context: which fields come back (ids, titles, links) and the intended two-step pattern with fetch. It stops short of describing result limits or ordering, which keeps it from a 5.

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?

Three tight sentences with no filler; the return shape and the follow-up tool are stated up front before the routing advice. The only cost is that the query-parsing rule and the 'prefer search_doctor_jobs' advice sit adjacent and read as partially conflicting.

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 single-parameter, no-output-schema tool this covers what an agent needs: what it searches, how the query string is interpreted, what comes back, and which sibling to use instead. The unresolved ambiguity about when filtering belongs here versus in search_doctor_jobs is the remaining gap.

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?

Schema coverage is 100% and the schema supplies an example, so the baseline would be 3. The description exceeds that by explaining the parsing rule — recognized specialty/career level/Bundesland tokens become filters while remaining words are treated as free text or a town — which is meaning the schema does not convey.

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?

The description states a specific verb and resource ("Search Klaro's doctor jobs in Germany") plus a scope qualifier ("for research clients") and the return shape (ids, titles, links). It also distinguishes itself from the sibling search_doctor_jobs by name, so an agent can route without opening either schema.

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?

It gives explicit routing guidance: "Prefer search_doctor_jobs for filtered searches," and names fetch as the follow-up for reading a result. The guidance is slightly muddied because the same sentence block says specialty/career level/Bundesland in this tool's query act as filters, so the boundary between this tool and search_doctor_jobs is not fully crisp.

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