Skip to main content
Glama

AMITA – Termin zur ärztlichen Abnehmberatung

Find AMITA practices

find_practices
Read-only

Use this when someone wants a doctor for medical weight loss or an AMITA practice in Germany. Returns the nearest AMITA practices with address, doctor, distance and next free time; locationFound is false when no place was recognised. Not for medical advice, prescriptions or emergencies.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_practices"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationNoSearch area the person named: city, district or German postcode, e.g. "Berlin Moabit" or "10551". Without it the search uses the approximate location the client shares.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / location / description
      Previous value: -"Only a place the person named as search area: city, district or German postcode, e.g. \"Berlin Moabit\" or \"10551\". Omit it to search near the approximate location the assistant shares."New value: +"Search area the person named: city, district or German postcode, e.g. \"Berlin Moabit\" or \"10551\". Without it the search uses the approximate location the client shares."
  2. Changed2 schema fields changed
    • changedInput schema / properties / location / description
      Previous value: -"Where the person lives or wants to go: city, district, street or German postcode, e.g. \"Berlin Moabit\" or \"10551\"."New value: +"Only a place the person named as search area: city, district or German postcode, e.g. \"Berlin Moabit\" or \"10551\". Omit it to search near the approximate location the assistant shares."
    • removedInput schema / required
      Removed value: -[
      -  "location"
      -]
  3. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already establish readOnly, non-destructive, closed-world behavior, and the description adds real context beyond them: the result payload contents, the 'nearest' ranking behavior, and the locationFound=false signal for unrecognised places. It also states the implicit fallback to the client's approximate location, which the agent needs in order to interpret an empty or partial result.

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?

Three short sentences with the trigger condition front-loaded, followed by return contents and then exclusions. Every sentence carries distinct information — routing, output shape, and scope limits — with no restatement of the name or title.

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?

With no output schema, the description takes on the burden of describing returns and does so concretely, including the edge-case flag and the location fallback. For a single-optional-parameter lookup tool, nothing an agent needs to call it correctly or interpret the response is missing.

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?

The single optional 'location' parameter is fully documented in the schema, including format examples and the fallback when omitted, so the description does not need to repeat it. The description's mention of location recognition failure adds marginal value but no syntax or format detail beyond the schema. Baseline 3 applies given 100% schema coverage.

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?

The description pairs a specific verb and resource ('find ... AMITA practices') with a concrete user intent ('wants a doctor for medical weight loss') and a geographic scope ('in Germany'). That intent framing plus the enumerated return fields (address, doctor, distance, next free time) makes it distinguishable from booking or slot-listing siblings without opening either 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?

It gives an explicit when-to-use trigger ('when someone wants a doctor for medical weight loss or an AMITA practice in Germany') and explicit when-not boundaries ('Not for medical advice, prescriptions or emergencies'). It stops short of naming the alternative tools (book_consultation, list_free_slots) for the post-search step, so routing between siblings is left partly implicit.

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