Skip to main content
Glama

MedaRep

Competitive landscape

incumbents
Read-onlyIdempotent

Which device companies engage a territory's surgeons for a family and how deeply, surgeons open or lunch-only (no company over $500), independent-channel candidates, employment mix, where cases are done (hospital, ASC, office) and the main sites of care.

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

Input Schema

NameRequiredDescriptionDefault
zipsNo5-digit ZIP codes forming a custom territory (as my_territories returns them).
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

C2.8/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 openWorld=false, so the safety profile is covered. The description adds genuine domain semantics beyond the annotations — the lunch-only threshold of 'no company over $500' is a definitional rule an agent would otherwise misread — but it says nothing about output shape, latency, data freshness, or what happens when a territory is empty.

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?

It is a single dense sentence with no filler, and the topic is front-loaded, but it is an unpunctuated run-on list of six concepts with no verb, so an agent must parse a comma chain to find the noun it needs. Compact, but structurally weak.

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 and six parameters on an analytical roll-up, the description must carry the burden of explaining what comes back; it lists content areas but not the record shape, granularity, or any caveats. Adequate to know roughly what is returned, insufficient to know how to consume it.

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 the schema already explains zips, metro, state, cities, family, and counties, including format examples. The description only echoes 'a territory's surgeons for a family,' adding no new parameter meaning beyond what the schema states; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description never states an action verb — it is a bare noun-phrase inventory of report contents (company engagement depth, surgeon segmentation, employment mix, sites of care). The resource is inferable as 'competitive incumbent landscape for a territory + procedure family,' and the enumerated dimensions do distinguish it from generic profile tools, but an agent must read the whole fragment to learn what the tool actually returns.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives. Siblings such as competitor_scorecard and company_profile plausibly overlap, and the description gives no basis for choosing between them — it does not even name the required family/territory scoping as a usage condition.

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