Skip to main content
Glama

MedaRep

Surgeons whose main company changed

switching
Read-onlyIdempotent

Surgeons in a territory whose main device company for a family (the one most engaged with them for its products) changed between the last two Open Payments years: who, from whom, to whom, with their Medicare cases, plus new and ended ties. Needs the product and company coverage add-on.

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

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 this a read-only, idempotent, closed-world operation, so the description's added value is what it discloses beyond them: the data source and time window (last two Open Payments years) and the shape of what comes back (who, from whom, to whom, Medicare cases, new and ended ties). It also flags a hard dependency — the product and company coverage add-on must be present — which is genuinely useful operational context not captured by any annotation.

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 a single dense sentence plus a short prerequisite clause, with the core condition front-loaded and each clause carrying distinct information (population, condition, comparison window, output columns, ties, add-on). It reads slightly run-on and could be broken for scanability, but there is no filler.

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 description correctly takes on the burden of sketching the return payload (surgeon, previous company, new company, Medicare cases, new/ended ties), and it covers the add-on prerequisite. What is missing is minor: nothing about ordering, row-limit behavior, or how empty results should be interpreted, though the limit default is in the schema.

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 all seven parameters (zips, metro, state, cities, counties, family, limit) are already documented with examples, and the baseline applies. The description explains the analytical concept of the 'family' and 'main company' but adds no syntax, format, or territorial-precedence detail beyond the schema.

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 states a precise analytical question — surgeons in a territory whose 'main' device company for a given family changed between the last two Open Payments years — and even defines 'main' as the company most engaged with them for its products. It does not explicitly contrast itself with plausible siblings such as ownership_changes or changes_since, so an agent still has to infer which change-tracking tool to pick.

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 by the framing (you want this when you care about company-switching surgeons in a territory) and it names a prerequisite — the product and company coverage add-on. There is no explicit when-not guidance or named alternative among the sibling tools, leaving routing decisions to inference.

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