Skip to main content
Glama

MedaRep

Surgeon profile

surgeon_profile
Read-onlyIdempotent

One clinician by NPI: Medicare cases by family and trend, cases under CMS's floor, forecast, peers, device payments by company and depth, research, practice and who decides, billing groups, sites, partners, movement, DME ordered, device-pointing prescribing, academic record, and the new-surgeon signal. Counts as a profile view on the caller's plan.

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": {
      "npi": "<npi>"
    },
    "name": "surgeon_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
npiYes10-digit NPI; use search to find it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so safety is covered. The description adds a genuinely non-derivable behavioral fact: the call "counts as a profile view on the caller's plan," which tells the agent this invocation consumes quota and should not be repeated casually. It stops short of stating behavior for an unknown or invalid NPI.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The body is one long comma-chained list of roughly fifteen data domains, which is poor scanning structure and buries the quota-consumption fact at the very end. The most decision-relevant information should lead, not trail a wall of nouns.

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?

With no output schema, the domain enumeration usefully previews what the profile returns (cases, trend, peers, device payments, sites, DME, academic record). Combined with the read-only annotations and a fully documented single parameter, an agent has enough to call it correctly; only error/failure behavior is 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 single parameter is documented in-schema, including the 10-digit format and the pointer to search, so the description need not repeat it. The description adds nothing about NPI semantics, which is acceptable at a 3 baseline.

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?

"One clinician by NPI" states the resource and its cardinality precisely, and the noun "clinician" implicitly separates it from the company_profile, facility_profile and practice_profile siblings. The remaining text is a data-domain inventory rather than a purpose statement, so the agent gets identity but not a crisp verb framing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use, when-not-to-use, or named alternative; the only routing hint ("use search to find it") lives in the schema, not the description. It also surfaces a "new-surgeon signal" without noting how that relates to the new_surgeons sibling, leaving the agent to guess at overlap.

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