Skip to main content
Glama

Stratalize Intelligence

Get Provider Market Intelligence

get_provider_market_intelligence
Read-only

Use when assessing physician supply in a market, evaluating a healthcare network expansion, or benchmarking provider density for population health strategy. Returns NPI registry physician counts and market structure by specialty and state. Example: Illinois cardiology — 847 cardiologists, 2.3 per 10,000 population vs 2.7 national median — below-median supply signals referral network expansion opportunity. Source: CMS NPI Registry synced data. $0.02 USDC per call.

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": {
      "specialty": "<specialty>",
      "state": "<state>"
    },
    "name": "get_provider_market_intelligence"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo
stateYes
specialtyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, open-world and non-destructive behavior, and the description adds genuinely new context: the underlying source (CMS NPI Registry synced data) and a per-call price of $0.02 USDC, which matters for a paid open-world call. It does not disclose data freshness/lag or result-size limits, so it is not fully transparent.

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?

Front-loaded with the use case, then the return, then a worked example, source, and price — each element earns its place. Slightly dense with the example embedded inline, but there is no filler.

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?

With no output schema, the description does the work of explaining returns (physician counts, per-10,000 density vs. national median, interpretation as supply signal). Gaps remain around what 'market structure' comprises and how the city parameter changes results, but it is largely sufficient for a three-parameter lookup.

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 0%, so the description must carry the burden: it confirms that specialty and state drive the query and the Illinois cardiology example hints at acceptable values. But the optional 'city' parameter is never mentioned, and no format is given for state (two-letter code?) or specialty (taxonomy vs. plain English).

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 verb and resource: 'Returns NPI registry physician counts and market structure by specialty and state.' That is concrete enough to separate it from a single-provider lookup, but it never names a sibling or explicitly contrasts with verification-style tools, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives three concrete when-to-use scenarios: assessing physician supply, evaluating network expansion, benchmarking provider density. Clear context, but there are no exclusions or named alternatives for adjacent questions such as individual provider verification or broader market briefs.

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