Skip to main content
Glama

Resident: Larchmont Village Oral Surgery

Prepare an LVOS staff follow-up request

prepare_appointment_request
Read-only

Validates a staff follow-up request for LVOS: first and last name, one contact method (phone or email), consultation type and an optional scheduling preference. Returns the normalized details, a disclosure of how they will be stored and emailed, an idempotency key and a confirmation token valid for 15 minutes. Stores nothing and sends nothing. Has no fields for date of birth, insurance, payment details or medical history.

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": {
      "practice_id": "<practice_id>",
      "first_name": "<first_name>",
      "last_name": "<last_name>",
      "contact": "<contact>",
      "appointment_type": "<appointment_type>"
    },
    "name": "prepare_appointment_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
contactYesExactly one way for staff to reach the patient.
last_nameYesPatient last name, for example Lopez.
first_nameYesPatient first name, for example Maria.
practice_idYesAlways LVOS (Larchmont Village Oral Surgery).
appointment_typeYesconsult: the practice's 'Consult' type (about 30 minutes). surgery_consult: its 'Surgery Consult' type (about 60 minutes). Staff confirm the right type.
preferred_day_or_timeNoOptional scheduling preference, for example 'weekday mornings'. Not an available or reserved slot. No clinical details.

Output Schema

NameRequiredDescriptionDefault
codeNo
reviewNo
statusNo
messageNo
practice_idNo
idempotency_keyNo
confirmation_tokenNo
retry_after_secondsNo
confirms_appointmentNo
confirmation_expires_atNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / appointment_type / description
      Previous value: -"consult: the practice's 'Consult' type (about 30 minutes). surgery_consult: its 'Surgery Consult' type (about 60 minutes). If unsure, use consult; staff confirm the right type."New value: +"consult: the practice's 'Consult' type (about 30 minutes). surgery_consult: its 'Surgery Consult' type (about 60 minutes). Staff confirm the right type."
    • changedOutput schema / properties / review / properties / appointment_type / description
      Previous value: -"consult: the practice's 'Consult' type (about 30 minutes). surgery_consult: its 'Surgery Consult' type (about 60 minutes). If unsure, use consult; staff confirm the right type."New value: +"consult: the practice's 'Consult' type (about 30 minutes). surgery_consult: its 'Surgery Consult' type (about 60 minutes). Staff confirm the right type."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnlyHint/destructiveHint=false annotations it discloses non-persistence, that nothing is emailed, the exact return payload (normalized details, storage/email disclosure, idempotency key, confirmation token with a 15-minute TTL), and the excluded sensitive data classes. This is substantially more than the annotations carry and consistent with them (idempotentHint=false is fine since the key is merely returned, not deduplicated).

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 tight sentences: what it validates, what it returns and does not do, then the compliance negative space. Every sentence carries information an agent would otherwise have to infer.

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?

An output schema exists, yet the description still names the returned artifacts, and the non-persistence and token-expiry facts are exactly what an agent needs before calling a prepare-style tool. Nothing material for correct invocation 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%, so the baseline is 3; the description still adds meaning by summarizing the required set ('one contact method (phone or email)', consultation type, optional scheduling preference) and by defining the parameter space negatively (no DOB, insurance, payment, or medical history), which reinforces additionalProperties=false.

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 ('Validates a staff follow-up request for LVOS') and enumerates the payload it covers. The clauses 'Stores nothing and sends nothing' cleanly separate it from the sibling send_appointment_request, so an agent knows this is the prepare-only step.

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?

The safety clauses ('stores nothing and sends nothing') plus the 15-minute confirmation token make the intended prepare-then-send workflow reasonably clear. It never names send_appointment_request explicitly nor states when-not to use it, so the routing is implied rather than prescribed.

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