Skip to main content
Glama

Resident: Larchmont Village Oral Surgery

Check LVOS scheduling status

get_available_appointments
Read-onlyIdempotent

Scheduling status for LVOS. Live availability is not connected, so the result is always integration_unavailable with no slots, plus the FlexBook online booking link, the phone number and the appointment types observed in the portal. No calendar is queried and nothing is booked. Takes practice_id LVOS.

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

Input Schema

NameRequiredDescriptionDefault
practice_idYesThe practice's exact, case-sensitive Resident registry ID from its connection documentation. Do not guess an ID from a practice name.

Output Schema

NameRequiredDescriptionDefault
codeNo
phoneNo
statusNo
messageNo
booking_urlNo
practice_idNo
available_slotsNoNull means availability was not checked; it does not mean the practice is fully booked.
retry_after_secondsNo
appointment_types_sourceNo
observed_appointment_typesNo
live_availability_accessibleNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Goes well beyond the annotations (which only say read-only, idempotent, non-destructive) by disclosing that live availability is not connected, that the result is ALWAYS integration_unavailable with zero slots, and that no calendar is queried. This prevents an agent from misreading an empty slot list as 'fully booked' – exactly the kind of behavioral disclosure that matters.

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?

The most important fact – availability is not connected and the result is always integration_unavailable – is front-loaded and unambiguous. The trailing 'Takes practice_id LVOS' is a dangling fragment that reads oddly but costs only one short clause.

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 an output schema, the description covers everything an agent needs: the constant status value, the absence of slot data, the fallback contact/booking channels, and confirmation that no side effects occur. Nothing material 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?

Schema coverage is 100% and the practice_id description already covers format, case sensitivity, and the anti-guessing rule. The description's only contribution is the fragment 'Takes practice_id LVOS,' which adds no meaning beyond the schema and is awkwardly worded. Baseline 3 is appropriate when the schema does all the work.

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?

The description names a specific resource (LVOS scheduling status) and states precisely what comes back: integration_unavailable, no slots, FlexBook link, phone number, and observed appointment types. It also separates this tool from booking actions with 'nothing is booked.' It stops short of naming the sibling tools that would actually book, so it lands at 4 rather than 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'No calendar is queried and nothing is booked' implies this is a fallback/lookup path rather than a booking path, which nudges the agent toward prepare_appointment_request or send_appointment_request. However, no alternative is named and there is no explicit 'use this when X, not when Y' statement. Usage is inferable but not spelled out.

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