Skip to main content
Glama

MedaRep

New surgeons not in the data yet

new_surgeons
Read-onlyIdempotent

Surgeons in a place the Medicare files cannot show yet: fellows who stayed (paid the assistant-at-surgery fee, now practising here) and recent joins of established groups. Each with its evidence and the signal's backtested accuracy.

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": {
      "family": "<family>"
    },
    "name": "new_surgeons"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipsNo5-digit ZIP codes forming a custom territory (as my_territories returns them).
limitNoHow many rows to return (default 25).
metroNoMetro area by name ("Charlotte") or 5-digit CBSA code (16740). Can cross state lines.
stateNoTwo-letter state code, e.g. NC. Omit when giving a metro or counties.
citiesNoCities within the state, to narrow it.
familyYesProcedure family key from coverage (e.g. knee-arthroplasty, lumbar-fusion) or a plain name.
countiesNo5-digit county FIPS codes forming a custom territory.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely non-obvious context: these are derived/projected entities rather than claim records, they come with supporting evidence, and each carries a backtested accuracy figure — an important reliability cue for an agent deciding how much to trust the output.

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?

Two sentences, purpose front-loaded, and the cohort breakdown is placed before the payload note. The parenthetical about the assistant-at-surgery fee is somewhat insider phrasing but does carry real definitional content, so little is wasted.

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 seven parameters, one required, and no output schema, the description does the important work of explaining who appears in the rows and what accompanies each row. What remains unstated — pagination default, geography-selector interaction — is already covered by the schema's own parameter descriptions.

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% and each of the seven parameters is documented in the schema itself, so the baseline of 3 applies. The description contributes nothing further about the required family key or how state/metro/counties/zips combine as territory selectors.

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 resource — surgeons that Medicare claims data cannot yet reveal — and splits it into two concrete cohorts (fellows who stayed and started billing assistant-at-surgery, and recent joins of established groups). An agent can grasp what set is returned, though the verb is only implicit (list) and no sibling such as surgeon_profile or new_clearances is named to sharpen the boundary.

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 implied rather than stated: by defining the population as surgeons absent from Medicare files, it signals the prospecting case where this tool beats a standard profile lookup. There is no explicit when-to-use statement, no exclusions, and no alternative tool named for the case where the surgeon is already visible in the data.

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