Skip to main content
Glama

Pa Medical Check Exclusion

pa_medical_check_exclusion
Read-onlyIdempotent

Is this healthcare provider precluded from the Pennsylvania Medical Assistance (Medicaid) program? Screens a person or business name, an NPI, a license number, and/or a federal EIN against the Pennsylvania Department of Human Services (DHS) Medicheck Precluded Providers List, the state-level counterpart to the federal HHS OIG LEIE (see the leie pack) for Pennsylvania specifically, and the sibling of ny_omig_check_exclusion (New York), ca_medical_check_exclusion (California), tx_medical_check_exclusion (Texas) and fl_medical_check_exclusion (Florida). Answers "is this provider precluded from Pennsylvania Medicaid", "check this NPI against the PA Medicheck list", or pre-payment/credentialing screening for a Pennsylvania Medicaid provider. An NPI, license-number, or FEIN match is an IDENTIFICATION (all three are exact, provider- or business-specific identifiers); a name match, even an exact one, is a CANDIDATE lead only, since this list carries no date of birth to tell same-named providers apart. Every match carries DHS's own Status field (Precluded, Terminated, Reinstated, Suspended, Withdrawal, and similar) and a currently_precluded flag DERIVED from that status, null with status_unknown:true on the minority of rows where DHS's own Status is blank, rather than a guess. This dataset covers everyone EVER precluded, not only those currently precluded. Pass npi, license, or fein to turn a name lead into an identification. Sourced from the Pennsylvania DHS Medicheck Precluded Providers List, keyless.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "Zeidler"
    },
    "name": "pa_medical_check_exclusion"
  }
}

Input Schema

NameRequiredDescriptionDefault
npiNoThe provider's 10-digit NPI, if known. An NPI match is an identification rather than a name lead, always pass it when known.
feinNoFederal Employer Identification Number (EIN) of the business, if known. An EIN match is an identification.
nameNoProvider or business name to screen, e.g. "John Smith" or "Acme Home Health Inc". Matched against the provider's individual name, business name, and any recorded alias, any word order.
limitNoMaximum matches to return (default 10, max 50).
licenseNoPennsylvania professional license number, if known, e.g. "AJ006399L". A license match is an identification.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / npi / description
      Previous value: -"The provider's 10-digit NPI, if known. An NPI match is an identification rather than a name lead — always pass it when known."New value: +"The provider's 10-digit NPI, if known. An NPI match is an identification rather than a name lead, always pass it when known."
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, open-world behavior, but the description adds substantive disclosure beyond them: the dataset includes everyone EVER precluded, not just current, and currently_precluded is derived from DHS's Status (null with status_unknown:true where Status is blank) rather than guessed. The remaining gap is return shape specifics like match counts or pagination beyond the limit parameter, which keeps it at 4 rather than 5.

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 core question and answerable queries, and nearly every clause carries information. It is long and has run-on parenthetical asides (the sibling list, the LEIE cross-reference) that could be tightened, but nothing is pure filler.

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 carries the return-value burden and does so: it explains the Status field values, the derived currently_precluded flag, and the null/status_unknown case. Combined with the source attribution and keyless note, an agent has everything needed to call and interpret this 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 match-confidence semantics the schema does not: NPI/license/FEIN are exact identifiers and constitute an identification, while a name match is only a candidate lead because the list carries no date of birth. That materially changes how an agent should interpret and act on inputs.

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?

States a specific question the tool answers ("Is this healthcare provider precluded from the Pennsylvania Medical Assistance program?") plus the exact source list (PA DHS Medicheck Precluded Providers List). It explicitly positions itself against named siblings (ny_omig, ca_medical, tx_medical, fl_medical and the federal LEIE pack), so an agent can disambiguate without opening schemas.

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 concrete when-to-use triggers (pre-payment/credentialing screening for a PA Medicaid provider) and an explicit escalation path: "Pass npi, license, or fein to turn a name lead into an identification." It also names the neighboring jurisdictions' tools so an agent knows when a different state tool is the right call.

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.