Skip to main content
Glama

MedaRep

Market size and outlook

market_outlook
Read-onlyIdempotent

A family's market in a place: Medicare cases by year, the all-Medicare estimate, the forecast to 2030 with ranges, the 65+ population and its growth, and per-metro or per-county supply, access and demand index.

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

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

A3.7/5.0
Behavior4/5

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

The annotations already establish that this is a safe, read-only, idempotent query. The description adds useful behavioral context by specifying the returned content, including historical Medicare cases, forecast ranges to 2030, population growth, and metro/county-level indices, which helps the agent understand what data it will receive.

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?

The description is a single dense sentence that front-loads the core concept and then enumerates the returned metrics. It contains no filler, though the long list could be more scannable if structured differently.

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 tool with no output schema and six parameters, the description does a good job of explaining the returned market metrics and geographic granularity. It stops short of clarifying how overlapping geographic selectors should be combined or what caveats apply to the forecast ranges.

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 six parameters are already well documented. The description reinforces that the tool operates at a family and place level and that supply/access/demand indices are per-metro or per-county, but it does not add guidance on how to combine or prioritize zips, metro, state, cities, and counties.

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 clearly identifies the resource as market size and outlook for a procedure family in a geographic area, and lists the specific metrics returned, including Medicare cases, the all-Medicare estimate, forecast to 2030, 65+ population, and supply/access/demand indices. It does not explicitly differentiate this tool from potentially overlapping siblings such as coverage or family_coverage, and it opens with a noun phrase rather than a clear verb.

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 'A family's market in a place,' suggesting the tool is for market sizing and outlook. However, there is no explicit when-to-use guidance, no mention of alternatives, and no explanation of when to prefer this over sibling tools.

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