Skip to main content
Glama

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.7/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: the upstream data source (CMS NPI Registry synced data) and a per-call price of $0.02 USDC, which matters for cost-aware invocation. It does not discuss freshness/lag of the synced data or rate limits.

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 when-to-use clause, then output, then a concrete example, then source and price. Dense but every clause carries information; the worked example is long but illustrates the return shape that no output schema provides.

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 usefully sketches the return shape (counts, per-10k density, national median comparison) and pricing. The main gap is operational detail on parameter formats and geographic scope (city vs state interaction), which an agent would need before calling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three parameters, so the description must carry the burden. It gestures at "specialty and state" but gives no format guidance (two-letter code vs full state name, taxonomy/exact-match rules for specialty) and never mentions the optional city parameter at all.

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 and output ("NPI registry physician counts and market structure by specialty and state"), which is concretely different from the sibling get_npi_provider_verification (individual lookup). It never explicitly contrasts with that sibling, so it falls 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?

Three explicit use scenarios are given (physician supply assessment, network expansion evaluation, provider density benchmarking for population health). There are no when-not conditions and no named alternative tools, so routing is clear but not exclusive.

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