Skip to main content
Glama

MedaRep

Who orders DME or prescribes

who_orders
Read-onlyIdempotent

Clinicians ranked by referred DME a supplier billed (bracing, bone growth stimulators, CGM, pumps, NPWT, dressings, compression, CPAP, CPM) or by device-pointing prescribing (rx-insulin, rx-anticoagulant, rx-bph, rx-glaucoma, rx-overactive-bladder), with specialty mix.

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": {
      "category": "<category>"
    },
    "name": "who_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNo
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.
categoryYesA DME category key or rx- drug class key from coverage.
countiesNo5-digit county FIPS codes forming a custom territory.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds that results are ranked and include a specialty mix, which is genuine output context, but it says nothing about pagination, default row count, permissions, or data-source recency beyond what the schema's limit field already shows.

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?

One dense sentence that front-loads the resource and ranking basis, with parenthetical enumerations that earn their space by conveying category breadth. It is a little heavy to parse but contains no filler.

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 eight parameters and no output schema, the description should say more about what a returned row contains (beyond 'specialty mix') and how ranking orders rows. Given the annotation coverage of safety traits, the definition is adequate to call the tool but leaves structural gaps for interpreting results.

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 88%, so the baseline is 3 and the schema already documents year, zips, limit, metro, state, cities, counties and category. The description only lays out the families of DME categories and rx- drug classes, which helps an agent pick a category but does not supply the actual key strings or explain how territory filters combine.

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 (clinicians) and an explicit ranking basis (referred DME billed by a supplier, or device-pointing prescribing), plus an added 'specialty mix' dimension. An agent can tell it produces a ranked clinician list rather than a market or territory ranking. It does not explicitly contrast itself with siblings such as rank_territory or coverage, but the purpose itself is unambiguous.

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 only implied: the category parameter note points at 'coverage' as the source of valid keys, which is a useful prerequisite hint. Nothing states when to choose this tool over related siblings (e.g., coverage, rank_territory), and there is no when-not guidance or mention of how the geography filters interact.

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