Skip to main content
Glama
Sign In

DoctoFam Medical Clinic

by com.doctofam
OverviewDiscussionsAdmin

List doctors and staff who take bookings

list_providers
Read-onlyIdempotent

Use this when someone asks which doctors, nurses or assistants patients can book at their practice, or who takes an appointment. Returns up to 100 staff ids and display names for one practice (no contact details or roles). Not for staff holidays or sick days.

Input Schema

NameRequiredDescriptionDefault
clinicIdYesPractice id: 24 lowercase hexadecimal characters

Output Schema

NameRequiredDescriptionDefault
providersYesIds and display names of staff with a doctor, nurse or assistant role, the ones the public booking page offers. Contact details, role records and clinical data are never returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedOutput schema / properties / providers / description
      Previous value: -"Display names of staff with a doctor, nurse or assistant role. Staff identifiers, contact details, role records and clinical data are never returned."New value: +"Ids and display names of staff with a doctor, nurse or assistant role, the ones the public booking page offers. Contact details, role records and clinical data are never returned."
    • addedOutput schema / properties / providers / items / properties / id
      Added value: +{
+  "description": "Id to book with, as book_appointment takes it",
+  "pattern": "^[0-9a-f]{24}$",
+  "type": "string"
+}
    • changedOutput schema / properties / providers / items / required
      Previous value: -[
-  "displayName"
-]New value: +[
+  "id",
+  "displayName"
+]
  2. Changed2 schema fields changed
    • changedInput schema / properties / clinicId / description
      Previous value: -"Clinic id (24-character hex)"New value: +"Practice id: 24 lowercase hexadecimal characters"
    • addedOutput schema / properties / providers / description
      Added value: +"Display names of staff with a doctor, nurse or assistant role. Staff identifiers, contact details, role records and clinical data are never returned."
  3. First observed

TDQS

A4.5/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 the safety profile is covered. The description adds genuinely useful behavioral context: results are capped at 100 and deliberately omit contact details and roles, which prevents an agent from promising fields that never come back. It does not discuss ordering or how to page past the 100 cap.

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, both front-loaded: the trigger condition comes first, then the return contract, then the exclusion. Nothing is redundant with the title or the schema, and there is no filler.

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?

For a single-parameter read tool with full annotation coverage and an output schema, the description supplies the trigger, the scope, the cap and the omissions. Nothing an agent needs in order to call it or set caller expectations is missing.

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 clinicId parameter is fully documented (24-char lowercase hex), so the schema carries the syntax burden. The description still adds meaning by stressing 'for one practice', clarifying that the id scopes the call to exactly one clinic rather than aggregating across a group.

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 (list) and resource (providers = doctors, nurses, assistants who take bookings), scoped to one practice, and explicitly bounds the payload (ids and display names, no contact details or roles). An agent can distinguish it from sibling tools such as list_rooms or get_clinic_availability 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 a concrete triggering condition ('when someone asks which doctors, nurses or assistants patients can book at their practice, or who takes an appointment') and a negative scope ('Not for staff holidays or sick days'). It stops short of naming the alternative tool an agent should use for holiday/absence questions, so it is not a full when/when-not/alternatives statement.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All DoctoFam Medical Clinic toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources