Skip to main content
Glama

Resident: Larchmont Village Oral Surgery

Read an LVOS practice document

fetch
Read-onlyIdempotent

Returns the full text and source URL of a Larchmont Village Oral Surgery document by its id, for example lvos-practice, with when the source was checked.

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": {
      "id": "<id>"
    },
    "name": "fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesA document id, for example lvos-practice or lvos-surgeons.

Output Schema

NameRequiredDescriptionDefault
idNo
urlNo
codeNo
textNo
titleNo
messageNo
metadataNo
retry_after_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"A document id returned by search, for example lvos-practice."New value: +"A document id, for example lvos-practice or lvos-surgeons."
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds modest behavioral value by disclosing that results include a source URL and a 'when the source was checked' freshness marker, hinting at possible staleness, but it says nothing about behavior on a missing or invalid id.

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?

One front-loaded sentence with no filler, stating resource, lookup key, and returned fields in that order. It is efficient, though the trailing clause about source-check timing reads slightly awkwardly and could be tightened.

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 one-parameter read tool with a full output schema and complete annotations, the description covers purpose and returned content sufficiently; return-format details are rightly left to the output schema. The only real omission is failure behavior for an unknown id.

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 single 'id' parameter is fully documented with the same examples ('lvos-practice') that appear in the description, so the description adds no meaning beyond the schema. Baseline 3 applies 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?

The description names a specific verb and resource — 'Returns the full text and source URL of a Larchmont Village Oral Surgery document by its id' — so an agent knows exactly what it retrieves. It does not explicitly contrast with the sibling 'search', which plausibly also surfaces document content, so sibling differentiation is left implicit.

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?

Usage is only implied: 'by its id' signals this is a lookup-by-identifier tool, which an agent can infer means fetching a known document rather than discovering one. There is no explicit when-to-use statement and no mention of how ids are obtained or what to do if the id is unknown.

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