Skip to main content
Glama

Klaro – Arztstellen in Deutschland

Compare doctor jobs

compare_jobs
Read-onlyIdempotent

Compare up to 5 doctor jobs side by side: reads each one in full, the same content as get_job_details.

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": {
      "ids": "<ids>"
    },
    "name": "compare_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesKlaro job ids (UUIDs).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description adds real behavioral context beyond them: each job is read in full and the content matches get_job_details. It omits failure handling (e.g., one invalid UUID) and result ordering, keeping 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence that front-loads the operation and limit, then closes with the equivalence to get_job_details. No filler or redundancy.

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 one required parameter, full schema coverage, and no output schema, the description needs to convey what comes back—it does so by pointing at get_job_details content. Only edge behavior for invalid or duplicate ids is left unstated.

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% and the schema already documents the UUID array and the maxItems of 5, so there is little room for the description to add meaning. The 'up to 5' restatement is consistent with the schema but not additive beyond it.

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 (compare) and resource (doctor jobs), gives the batch limit (up to 5), and clarifies what it reads by equating the content to get_job_details. An agent can distinguish it from get_job_details or search_doctor_jobs without opening any 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 comparison framing plus the note that the content equals get_job_details implicitly tells the agent this is the batch alternative to repeated detail calls. It stops short of explicitly saying 'use this instead of calling get_job_details N times' or stating when-not to use it.

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