Skip to main content
Glama

book_appointment

Book an available medical appointment slot for a patient. Validates slot availability using patient MRN and booking string, then returns the new appointment ID.

Instructions

Book an available slot for a specific patient.

patient_id is mandatory so a booking can never land on the wrong person's record. The portal validates the slot at booking time (read-before-write); if the slot is gone you get a clear error and nothing is booked. Returns the new appointment id on success.

Note: reporting_id defaults to empty. It's unverified whether the API requires it (the captured bookings carried one from the out-of-scope triage flow); if booking fails citing it, that's the likely cause.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
patient_idYesMRN of the patient to book for. REQUIRED — never guessed.
reporting_idNoReporting/correlation token. Whether the portal requires it is unverified (see NOTES.md); the in-scope search flow has no source for one, so leave empty unless you captured a value.
booking_stringYesThe `booking_string` of the slot to book (from search_slots).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
bookedYes
clinicNo
doctorNo
messageNo
slot_dateNo
appointment_idNo
Behavior5/5

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

No annotations provided, so the description fully covers behavior: read-before-write validation, error handling if slot is gone, return of appointment id, and the uncertainty of reporting_id. Comprehensive for a mutation tool.

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?

Well-structured with clear sections for purpose, parameter details, and behavior. A bit verbose but every sentence adds value. Could be slightly trimmed without losing meaning.

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 output schema exists (so return values are documented elsewhere), the description provides necessary operational details: slot validation, error behavior, and a practical note on reporting_id. Covers all essential aspects for an agent to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds significant value: explains why patient_id is required, and gives practical caveat about reporting_id (unverified requirement, leave empty). Goes beyond schema descriptions.

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?

Clearly states the tool books an available slot for a specific patient, with a specific verb and resource. Distinguishes from siblings like reschedule_appointment and search_slots by the unique action of booking.

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?

Provides clear context: patient_id is mandatory, slot validation occurs at booking time, and a caveat about reporting_id. Does not explicitly state when not to use, but the context is sufficient for an agent to decide.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mattijskersten/medimcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server