Skip to main content
Glama

Fragen eines Bereichs

get_assessment_questions
Read-onlyIdempotent

Use first when someone wants to estimate the German care grade (Pflegegrad) or asks "wie viele Punkte", "welchen Pflegegrad bekommt meine Mutter", "Pflegegrad berechnen", "Pflegegrad einschätzen", "Begutachtung vorbereiten". Returns the questions of one of the six assessment areas (Modul 1 Mobilität, 2 Verstehen und Sprechen, 3 Verhalten, 4 Selbstversorgung, 5 Krankheit und Behandlung, 6 Alltag und Kontakte) exactly as § 15 SGB XI Anlage 1 defines them, with the answer scale and the points per answer. Ask the user these questions, then pass the point values to calculate_pflegegrad. Call it once per area (1 to 6); the user may skip areas. Never ask for a name, diagnosis or birth date.

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": {
      "modul": "<modul>"
    },
    "name": "get_assessment_questions"
  }
}

Input Schema

NameRequiredDescriptionDefault
modulYesBereich 1 bis 6.

Output Schema

NameRequiredDescriptionDefault
nameYes
modulYes
fragenYes
hinweisNo
quellenYes
beispielNo
disclaimerYes
gewichtungNo
zusatzfragenYes
antwortformatYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/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 genuine context beyond that: the questions are returned exactly as § 15 SGB XI Anlage 1 defines them, including answer scale and point values, and it imposes a privacy constraint ('Never ask for a name, diagnosis or birth date'). It stops short of describing response shape, though the output schema covers that.

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 use case before mechanics, and every clause carries weight (triggers, scope, downstream tool, privacy rule). It is a dense single block rather than cleanly separated sentences, and the long quoted-phrase list adds retrieval value at some cost to readability.

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?

Given a one-param tool with a full output schema and rich annotations, the description covers everything an agent needs: when to call, how many times, which modules exist, what the response contains, and what to do with the result. No material gap remains.

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 single param is documented as 'Bereich 1 bis 6', so the baseline would be 3. The description goes further by naming each of the six modules with its number (1 Mobilität … 6 Alltag und Kontakte), turning an opaque integer into a meaningful selector.

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+resource (returns the assessment questions of one of six modules) and enumerates all six areas by name, so the agent knows exactly what content comes back. It is clearly distinguishable from calculate_pflegegrad and get_pflegegrad_facts, which it explicitly routes to.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger condition ('Use first when someone wants to estimate the German care grade'), sample user phrasings, the call pattern ('once per area, 1 to 6, areas may be skipped'), and names the downstream tool (calculate_pflegegrad) that consumes the points. Both when-to-use and how-it-sequences are covered.

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