Skip to main content
Glama

Resident: Larchmont Village Oral Surgery

Search LVOS practice information

search
Read-onlyIdempotent

Searches public information about Larchmont Village Oral Surgery in Los Angeles, including its location, hours, surgeons, services and how to book. Returns matching document ids, titles and source URLs; an empty list means no match.

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch words, for example 'wisdom teeth', 'office hours' or 'Dr. Balacky'. Patient names and contact details are not used.

Output Schema

NameRequiredDescriptionDefault
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Search words, for example 'wisdom teeth', 'office hours' or 'oral surgeon Larchmont Los Angeles'. Do not include patient names or contact details."New value: +"Search words, for example 'wisdom teeth', 'office hours' or 'Dr. Balacky'. Patient names and contact details are not used."
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds the result shape (document ids, titles, source URLs) and the empty-list semantics, which is modest added value given an output schema already exists; it says nothing about result limits, ranking, or matching behavior.

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?

Two tight sentences: the first defines scope and covered content, the second defines the return contract. No filler, and the most important information is front-loaded.

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-only search with full annotation coverage and an output schema, the definition supplies enough to invoke it correctly. The only meaningful omission is routing guidance against the structured sibling tools, which is a usage gap rather than a missing behavioral fact.

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?

Only one parameter with 100% schema coverage, where the schema already gives examples ('wisdom teeth', 'office hours', 'Dr. Balacky') and excludes patient names. The description adds only the general 'public information' scope, which is baseline-level value when the schema does the heavy lifting.

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?

States a specific verb and resource ("Searches public information about Larchmont Village Oral Surgery") and enumerates the covered facets: location, hours, surgeons, services, booking. It does not differentiate from overlapping siblings like get_services or get_provider_information, which an agent would need to disambiguate free-text search from structured lookup.

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?

Implied usage is clear enough for a search tool — free-text lookup across the practice's public info — and the description notes that an empty list means no match, hinting at fallback behavior. However, it never states when to prefer this over the sibling structured tools (get_services, get_provider_information) or what to do when results are empty.

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