Skip to main content
Glama

Klaro – Arztstellen in Deutschland

Get job details

get_job_details
Read-onlyIdempotent

Read one job in full as Markdown (employer, place, contract, tasks, requirements, offer) by the id search_doctor_jobs returned. The employer's original advert stays the binding source.

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": {
      "id": "<id>"
    },
    "name": "get_job_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesKlaro job id (UUID).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds genuinely new context beyond that: the payload is rendered as Markdown and the employer's original advert remains the authoritative source, which warns the agent about provenance and possible staleness — but it says nothing about behavior for an unknown or malformed id.

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 primary action and returned content are front-loaded, and the authoritative-source caveat follows as a secondary note.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-id read with full schema coverage and complete annotations, the description supplies everything needed: the return format, the fields included, where the id comes from, and a data-authority caveat. No output schema exists, and the description adequately compensates by naming the returned sections.

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?

With one parameter at 100% schema coverage, the schema already explains that id is a Klaro UUID. The description's contribution is provenance — the id must come from search_doctor_jobs output — which is meaningful linkage the schema does not express.

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?

States a specific verb and resource ('Read one job in full as Markdown') and enumerates the returned fields (employer, place, contract, tasks, requirements, offer). It also ties itself to the sibling that supplies the identifier, so an agent can distinguish it from search_doctor_jobs or compare_jobs without opening a 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?

The phrase 'by the id search_doctor_jobs returned' establishes the prerequisite workflow: search first, then fetch details. It does not explicitly exclude alternatives (e.g., 'use compare_jobs for multiple postings'), so it stops short of full when/when-not guidance.

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