Skip to main content
Glama

Resident: Larchmont Village Oral Surgery

Get LVOS practice information

get_provider_information
Read-onlyIdempotent

Public information about Larchmont Village Oral Surgery (LVOS), an oral surgery practice in Larchmont Village, Los Angeles: address, phone, office hours and time zone, services, the online booking link, and whether staff follow-up requests are enabled. Facts come from the practice website; null fields are unknown. Takes practice_id LVOS. Does not include appointment availability.

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_provider_information"
  }
}

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
providerNo
retry_after_secondsNo
appointment_requestsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the description is not required to restate safety. It does add genuinely useful context beyond them: facts are sourced from the practice website and null fields mean unknown, which tells the agent how to interpret gaps rather than retrying. It does not describe caching or freshness of the website-derived facts, which would have completed the picture.

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 return contents are front-loaded in a single dense clause, followed by two short clarifiers on provenance/null semantics and the availability exclusion. Every sentence earns its place; the only soft spot is the trailing 'Takes practice_id LVOS' fragment, which reads as an afterthought.

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?

This is a simple single-parameter read tool with full schema coverage and an output schema, so return-value detail is unnecessary. The description covers scope, provenance, null semantics, and the availability boundary, leaving only freshness of website-derived facts unaddressed.

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 schema already documents the exact, case-sensitive registry ID and warns against guessing from a practice name, so the description need not repeat that. Its contribution, 'Takes practice_id LVOS,' adds a fixed-value hint but sits in mild tension with the schema's anti-guessing warning, so it neither compensates nor informs beyond the baseline 3.

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?

The description names a specific verb and resource and then enumerates exactly what is returned: address, phone, office hours and time zone, services, booking link, and follow-up-request flag. It also draws an explicit boundary against the closest sibling by stating it does not include appointment availability, so an agent can distinguish it from get_available_appointments without opening either 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?

The exclusion of appointment availability gives a clear signal that scheduling questions belong elsewhere, and the LVOS-specific framing makes the intended context obvious. It stops short of naming get_available_appointments or get_services as the alternatives, so the routing is implied rather than 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