Skip to main content
Glama

StatuteWire

screen_practitioner

Read-only

Screens one practitioner: state license status and board discipline flags (only for states that are live; sandbox keys get SAMPLE data for every state), identity check against CMS NPPES, and exclusion screening (OIG LEIE, SAM.gov and the state Medicaid lists that are live), with an evidence receipt. Requires NPI + first name + last name + state; if the names you give do not match the record, the result is blocked, not warned. The output lists which sources returned CLEAR and which did not; a source that is not CLEAR (including NOT_CHECKED and COULD_NOT_CHECK) must never be reported as clear. Counts as one lookup against the key's quota or prepaid balance (1 check), exactly as GET /api/v1/sanctions does. Not covered: states that are not live, licenses of staff without an NPI (use screen_roster), anything not on the official lists. A possible match is for a person to confirm with the official source. Needs an API key (Authorization: Bearer sw_live_… or sw_test_…); without one it returns an error that points to how_to_get_access.

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": {
      "npi": "<npi>",
      "first_name": "<first_name>",
      "last_name": "<last_name>",
      "state": "<state>"
    },
    "name": "screen_practitioner"
  }
}

Input Schema

NameRequiredDescriptionDefault
npiYesThe 10-digit National Provider Identifier (NPI).
freshNotrue skips the 120-day cache and queries the source again.
stateYesTwo-letter state code, or eNLC for the nursing compact (sample data only).
last_nameYesThe practitioner's last name, as on their license.
first_nameYesThe practitioner's first name, as on their license.
professionNoClinical profession, to scope the board search.
license_numberNoRequired for states verified live; the error detail shows the format.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations: discloses quota/balance consumption ("Counts as one lookup... 1 check"), the 120-day cache, sandbox-vs-live key behavior, and the blocking (not warning) behavior when names do not match. It also defines result semantics — NOT_CHECKED and COULD_NOT_CHECK must never be reported as clear — which is exactly the kind of context an agent needs to interpret output safely. No contradiction with readOnlyHint, since this is a read-only screening query whose cost is a quota debit, not a data mutation.

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 purpose, then preconditions, output semantics, cost, exclusions and auth — a sensible priority order. It is dense but nearly every clause carries information; the heavy parenthetical in the first sentence is the only place readability suffers.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 still explains the shape of the result (which sources returned CLEAR and which did not) and the interpretation rule for non-CLEAR statuses. Combined with auth requirements, cost, caching and coverage limits, nothing material is missing for a 7-parameter screening tool.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: it explains why first_name/last_name are required (a name mismatch blocks the result rather than warning), clarifies that `state` must be a live state, and ties `fresh` implicitly to the stated 120-day cache. It does not explain `profession` scoping or the license_number-per-state rule beyond what the schema already says.

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

Purpose5/5

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

Opens with a specific verb and resource ("Screens one practitioner") and enumerates exactly which checks run: state license status, board discipline flags, NPPES identity, OIG LEIE/SAM.gov/state Medicaid exclusions. It also states the scope boundary ("only for states that are live") and contrasts with the sibling screen_roster, so an agent can distinguish it without opening the schema.

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

Usage Guidelines5/5

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

Gives explicit preconditions (NPI + first name + last name + state, API key), explicit exclusions ("Not covered: states that are not live, licenses of staff without an NPI (use screen_roster), anything not on the official lists"), and routes the agent to how_to_get_access when unauthenticated. It also tells the caller what to do with a possible match (confirm with the official source).

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