Skip to main content
Glama

Resident: Larchmont Village Oral Surgery

Get LVOS oral surgery services

get_services
Read-onlyIdempotent

Oral surgery services offered by LVOS, such as wisdom teeth removal, dental implants, full-arch implants, bone grafting, sinus lifts, biopsies, sedation and emergencies, with short descriptions and links to the practice's pages. General information only; not medical advice, treatment eligibility or availability. 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_services"
  }
}

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
messageNo
servicesNo
practice_idNo
source_checked_onNo
retry_after_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 meaningful context beyond them: what the payload contains (descriptions and page links) and a scope disclaimer that prevents the agent from treating output as medical advice or a booking signal.

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 resource identification is front-loaded, followed by the content list and then the disclaimer, so the agent gets purpose before caveats. The sentence is dense but every element (services, return content, disclaimer) carries information; nothing is redundant filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 a full output schema, the definition covers purpose, return shape, and usage limits. The only thing left implicit is which sibling to use for availability and booking, so a small gap remains.

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 parameter already documents the exact-case registry ID and the 'do not guess' rule. The description's 'Takes practice_id LVOS' only restates the single required value, adding no new syntax or format meaning. Baseline 3 is appropriate.

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 (oral surgery services) with the owning practice (LVOS) and enumerates the actual content (wisdom teeth removal, implants, bone grafting, etc.) plus the return shape (short descriptions and links). It is unambiguous, though it does not explicitly contrast itself with the appointment-oriented siblings.

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 draws a clear boundary: general information only, not medical advice, treatment eligibility, or availability. That last clause implicitly steers availability questions toward get_available_appointments. It stops short of naming an alternative tool outright.

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