Skip to main content
Glama

MedaRep

Why now: who may be worth a call this week

opportunities
Read-onlyIdempotent

A territory's surgeons ranked by dated reasons they may be worth a call now: a recall or rising MAUDE reports at a company engaged with them for these products (possible supply or service disruption, not a finding of fault), a new FDA clearance for their main company (read as new entrant, new system or line extension), engagement moving to a different main company, a move or practice change, a new surgeon not in the Medicare files yet, a growing practice with no device ties. Each with its evidence, a warm introduction from the rep's customers if one exists, the lists it is already on, and a next step. Give a saved territory by name (its family is used unless one is given) or a family and a place; since (YYYY-MM-DD, default a year ago) keeps the reasons recent, e.g. the date of the last brief. Recall, clearance and switching reasons need the coverage add-on.

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

Input Schema

NameRequiredDescriptionDefault
zipsNo5-digit ZIP codes forming a custom territory (as my_territories returns them).
limitNoHow many surgeons (default 15).
metroNoMetro area by name ("Charlotte") or 5-digit CBSA code (16740). Can cross state lines.
sinceNoOnly reasons dated on or after this day, YYYY-MM-DD. Default: a year ago.
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.
territoryNoA saved territory's name or id from my_territories, instead of a place.

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?

Beyond the read-only and idempotent annotations, it discloses reason categories, a no-fault caveat for recall/MAUDE signals, inclusion of evidence, warm introductions, lists, and next steps, plus the coverage add-on requirement for recall, clearance, and switching reasons. It leaves output format and failure behavior under-specified but adds substantial behavioral context.

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

Conciseness3/5

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

Purpose is front-loaded, but the first sentence is a long comma-heavy enumeration of reason types that is harder to scan than a structured list. It contains little pure filler, yet the dense packaging weakens readability.

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 a nine-parameter tool with no output schema, it covers what the result contains (surgeons, reasons, evidence, introductions, lists, next step), scope options, recency, and add-on dependency. Some operational details such as output field shape and add-on failure behavior remain unstated.

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 complete, and the description still adds semantics: a saved territory name implies its family unless family is passed, family plus place is an alternative route, and since defaults to a year ago and controls reason recency. It does not elaborate most place parameters, but the schema already carries those definitions.

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?

States a specific resource and ranking criterion: a territory's surgeons ranked by dated reasons they may be worth a call now, with evidence and a next step. It does not explicitly contrast with siblings such as new_clearances or switching, so it is clear but not fully differentiated by name.

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?

Provides input-shape guidance (saved territory or family plus place) and a recency default, which implies this is a weekly call-prioritization view. It does not say when to choose this over sibling tools or what happens if the coverage add-on is not present.

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