Skip to main content
Glama

AMITA – Termin zur ärztlichen Abnehmberatung

Show free consultation times

list_free_slots
Read-only

Use this when the person wants appointment times at one AMITA practice. Returns its free consultation times for the next two weeks (Europe/Berlin).

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>"
    },
    "name": "list_free_slots"
  }
}

Input Schema

NameRequiredDescriptionDefault
practiceIdYesId of an AMITA practice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / practiceId / description
      Previous value: -"practiceId returned by find_practices."New value: +"Id of an AMITA practice."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so safety is covered; the description adds genuinely new behavior: a two-week horizon and the Europe/Berlin timezone, both of which affect how an agent presents results. It omits any indication of what a slot record contains or how many slots come back, 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.

Conciseness5/5

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

Two sentences, zero filler, with the usage trigger front-loaded and the return scope and timezone following. Nothing is redundant with the title or annotations.

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 one-parameter read tool with annotations covering safety and no output schema, the definition supplies the two facts an agent most needs: the lookahead window and the timezone. What remains unsaid — slot granularity and whether results are practitioner-specific — is minor for this complexity level.

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 coverage is 100% and the single practiceId parameter is already documented as "Id of an AMITA practice." The phrase "at one AMITA practice" reinforces that exactly one practice is queried, but adds no format, sourcing, or validation meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: it returns free consultation times for one named practice, scoped to the next two weeks in Europe/Berlin. The scope is precise enough to distinguish it from booking or practice-search tools, though it never names those siblings explicitly.

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?

"Use this when the person wants appointment times at one AMITA practice" gives a clear triggering condition tied to the practiceId requirement. It stops short of saying when not to use it or naming book_consultation/find_practices as the alternative path.

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