Skip to main content
Glama

Find rated doctors for a procedure near a place

find_doctors_for_procedure
Read-onlyIdempotent

Finds rated doctors for a procedure near a US city or ZIP code, for example a knee replacement surgeon near me. Returns up to 5 doctors in OpenHealth's published order: predicted result at the doctor's affiliated hospitals, then procedures a year, then distance. Each doctor has a letter grade, a yearly procedure count, a distance and a main hospital. The grade describes the hospitals, not the doctor's own skill. Only some procedures have ratings. The others return not_scored with the reason. The radius is 10, 25 or 50 miles.

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": {
      "procedure": "<procedure>",
      "place": "<place>"
    },
    "name": "find_doctors_for_procedure"
  }
}

Input Schema

NameRequiredDescriptionDefault
placeYesA US city with its state, such as Columbus, OH, or a 5-digit ZIP code.
procedureYesThe procedure, as an id such as knee-replacement or in plain words such as knee replacement.
radius_milesNoThe search radius in miles: 10, 25 or 50. The default is 25.

Output Schema

NameRequiredDescriptionDefault
dataNo
notesNo
statusYes
sourcesNo
page_urlNo
release_idNo

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior5/5

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

It goes well beyond what the readOnlyHint, idempotentHint and openWorldHint=false annotations already declare. It discloses the result cap (up to 5), the ordering of results (predicted result, then procedures per year, then distance), the not_scored fallback for procedures that are not rated, and the crucial caveat that 'the grade describes the hospitals, not the doctor's own skill'. That last point is a genuine interpretation risk that the agent could not infer from the schema or annotations.

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?

It is front-loaded with the action and scope, and each subsequent sentence carries real information: result cap, ordering, the grade caveat and the not_scored behavior. The 'for example a knee replacement surgeon near me' clause is close to padding, but it doubles as disambiguation for the procedure parameter.

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?

Because it is a read-only search tool, the tool is simple; the description covers the search scope, the return cap, the ordering, an interpretation caveat, and the case where no rating exists. An output schema exists, so return values need not be spelled out in full. Nothing an agent needs in order to call it correctly 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 description coverage is 100%, so place, procedure and radius_miles are already fully documented, including the accepted formats and the enum of 10/25/50 miles. The description largely restates these ('near a US city or ZIP code', 'The radius is 10, 25 or 50 miles') without adding syntax or constraints beyond the schema. The baseline of 3 is appropriate 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.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Finds rated doctors for a procedure') plus the geographic scope ('near a US city or ZIP code'), which no sibling tool, such as get_doctor or search_providers, does in this form. The example ('knee replacement surgeon near me') removes any ambiguity for an agent.

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 gives a clear context ('for example a knee replacement surgeon near me') and a key conditional ('Only some procedures have ratings. The others return not_scored with the reason'), which warns the agent about partial results. It does not name alternatives or exclusions, so it falls short of a 5, which would require an explicit alternative such as list_procedures or search_providers.

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