Skip to main content
Glama

MedaRep

Rank a territory's surgeons

rank_territory
Read-onlyIdempotent

Surgeons operating in a place for a procedure family, ranked by Medicare cases weighted by how deep their payment ties to a device company are: cases and change, MA-adjusted trend, practice and employment, likely incumbent (the company most engaged with them, by Open Payments) and relationship depth, payments, sites of care, and all-payer estimates where the plan includes them.

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": "rank_territory"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoMedicare data year; defaults to the latest.
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

B3.2/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive, and the description adds real substance beyond them: the ranking methodology, the fields returned (cases, trend, incumbent, payments, sites of care), and the conditional caveat 'all-payer estimates where the plan includes them.' It does not mention default row count or pagination, which are left to the schema.

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?

Everything is crammed into one long run-on sentence with nested parentheticals and a trailing field list. The core ranking idea is not front-loaded; an agent must parse past the field inventory to find the purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, enumerating returned fields is justified and partially done. However, for an eight-parameter spatial query the description never explains how territory selectors interact or what happens with the default year/limit, leaving gaps an agent would have to guess at.

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%, so the schema already documents all eight parameters. The description adds only the vague notion of 'a place' without clarifying how zips, counties, metro, state, and cities combine into a territory, so it neither compensates nor detracts.

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 ('Surgeons ... ranked by Medicare cases') and pins down the ranking metric (weighted by payment-relationship depth), which is more than a restatement of the name. It stops short of distinguishing itself from siblings like incumbents or territory_changes, so an agent must infer 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 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 alternative named. 'Surgeons operating in a place for a procedure family' implies the input shape but gives no guidance on choosing this over incumbents, new_surgeons, or territory_changes.

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