Skip to main content
Glama

AMITA – Termin zur ärztlichen Abnehmberatung

Book first consultation

book_consultation
Idempotent

Use this when the person has chosen a practice and time and wants to book. Books the non-binding first consultation with a doctor with the person's own name, e-mail and phone number and their agreement to AMITA's privacy policy; AMITA e-mails the confirmation. Cannot change or cancel an appointment.

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": {
      "practiceId": "<practiceId>",
      "slotIso": "<slotIso>",
      "firstName": "<firstName>",
      "lastName": "<lastName>",
      "email": "<email>",
      "phone": "<phone>",
      "privacyPolicyAccepted": "<privacyPolicyAccepted>"
    },
    "name": "book_consultation"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYes
phoneYesPhone number for the practice team, ideally mobile.
slotIsoYesStart of a free consultation slot of this practice (ISO 8601).
lastNameYes
firstNameYes
practiceIdYesId of an AMITA practice.
privacyPolicyAcceptedYesWhether the person agreed to AMITA's privacy policy (https://abnehmen-mit-arzt.de/privacy/).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / practiceId / description
      Previous value: -"practiceId returned by find_practices."New value: +"Id of an AMITA practice."
    • changedInput schema / properties / privacyPolicyAccepted / description
      Previous value: -"True only after the person agreed to AMITA's privacy policy (https://abnehmen-mit-arzt.de/privacy/)."New value: +"Whether the person agreed to AMITA's privacy policy (https://abnehmen-mit-arzt.de/privacy/)."
    • changedInput schema / properties / slotIso / description
      Previous value: -"slotIso of a free slot from list_free_slots, unchanged."New value: +"Start of a free consultation slot of this practice (ISO 8601)."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=true, openWorldHint=true) the description discloses that the consultation is non-binding, that AMITA e-mails the confirmation, that the contact data must be the person's own, and that privacy-policy consent is mandatory. It also clarifies that the booking cannot later be changed or cancelled, which is the practical consequence an agent needs before committing a user.

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 sentences, front-loaded with the usage trigger, then the effect and the hard limitation. Every clause carries information an agent would otherwise have to guess.

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?

All seven required parameters are semantically covered and the side effect (confirmation e-mail) is stated, which is strong for a write tool. Since there is no output schema, the description would ideally say what the call returns (e.g. an appointment or booking identifier), which 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?

With only 57% schema description coverage, the description usefully carries meaning for the undocumented fields: it maps the name, e-mail and phone parameters to the constraint that they must be the person's own details, and ties privacyPolicyAccepted to the agreement requirement. It adds no detail on practiceId or slotIso provenance beyond what the schema already says, which keeps it off a 5.

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 ('Books the non-binding first consultation with a doctor') and narrows scope to the first consultation only. The opening clause 'when the person has chosen a practice and time' implicitly positions it as the step after find_practices and list_free_slots, so an agent can distinguish it from the siblings 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?

Gives an explicit trigger condition ('when the person has chosen a practice and time and wants to book') plus an explicit exclusion ('Cannot change or cancel an appointment'). It stops short of naming what an agent should do instead for a reschedule or cancellation, so the alternatives half of the guidance is missing.

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