Skip to main content
Glama

MedaRep

Warm introductions

warm_paths
Read-onlyIdempotent

Which of the rep's own customers (marked on MedaRep) can open a door to a surgeon: partners now or before, the same hospital, the same device company, or a partner in common, with each path's strength. Give one NPI, or a family and a place for the territory's warmest targets and its lookalikes: surgeons who fit the pattern of the rep's customers there (setting, employment, volume, company), connected or not.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "warm_paths"
  }
}

Input Schema

NameRequiredDescriptionDefault
npiNoA target's 10-digit NPI. Omit to rank a territory's targets.
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.
familyNoProcedure 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.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. Beyond that, the description adds genuine context the annotations do not: paths carry a strength value, the source universe is limited to customers "marked on MedaRep," and territory mode returns connected and unconnected surgeons alike. Return payload shape is only sketched, not specified.

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, front-loaded with the relationship concept and then the input modes, with no filler. The second sentence is dense with stacked parentheticals, which slightly taxes parsing, but each clause carries information.

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?

For an 8-parameter, zero-required query tool with full schema coverage and no output schema, the description covers both modes, the data source, and the meaning of the returned strengths and lookalikes. Remaining gaps (pagination via limit, exact row shape) are minor given the schema documents limit itself.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so a baseline of 3 applies; the description earns above that by explaining the mutually exclusive input modes (one NPI, or family plus a place) and by defining what the territory mode yields — surgeons matching the rep's customers on setting, employment, volume and company, "connected or not," which the schema does not convey.

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 specific analytical resource: which of the rep's own MedaRep-marked customers can connect to a surgeon, via named relationship types (partners now or before, same hospital, same device company, common partner), plus a second territory-ranking mode with lookalikes. That is far more specific than the bare name and distinguishes it from list-style siblings like my_customers, though the connecting verb is implied by "which ... can open a door" rather than stated.

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?

It clearly separates the two invocation modes (single NPI versus family + place for territory ranking), which is real usage guidance. It never says when this is preferred over alternatives such as my_customers, my_accounts, or search, and offers no exclusions, so the guidance is implied rather than explicit.

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