Skip to main content
Glama

Tx Medical Exclusion Coverage

tx_medical_exclusion_coverage
Read-onlyIdempotent

What the Texas HHSC OIG Medicaid Provider Exclusions data covers and how current it is: total exclusions ever recorded, how many are currently excluded vs. reinstated, how many carry an NPI or license number, how many distinct occupations appear, the oldest and newest exclusion dates, and when this pack's copy was captured. Use to check the screening data is fresh enough to rely on before a compliance decision, and to see the one-line notes on the free-text reason field and the ever-vs-currently-excluded distinction. Pass year (e.g. 2025) or start_date/end_date to instead COUNT how many exclusions have an effective date in that year or range, counted over the whole 13,000+ row list, not a page, answers "how many Texas HHSC OIG exclusions took effect in 2025". The response names the date field counted (excluded_since / HHSC's StartDate, never added_date, which answers a different question and gives a different number). Sourced from the Texas HHSC OIG Exclusions Database File, 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": "tx_medical_exclusion_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoCount records whose date field falls in this calendar year (e.g. 2025), counted over the WHOLE list, not a page. Ignored if start_date/end_date are given.
end_dateNoInclusive range end, YYYY-MM-DD. Use with start_date for a custom date range instead of a calendar year.
start_dateNoInclusive range start, YYYY-MM-DD. Use with end_date for a custom date range instead of a calendar year.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / examples
      Previous value: -[
      -  {}
      -]New value: +[
      +  {},
      +  {
      +    "year": 2025
      +  }
      +]
    • addedInput schema / properties / end_date
      Added value: +{
      +  "description": "Inclusive range end, YYYY-MM-DD. Use with start_date for a custom date range instead of a calendar year.",
      +  "type": "string"
      +}
    • addedInput schema / properties / start_date
      Added value: +{
      +  "description": "Inclusive range start, YYYY-MM-DD. Use with end_date for a custom date range instead of a calendar year.",
      +  "type": "string"
      +}
    • addedInput schema / properties / year
      Added value: +{
      +  "description": "Count records whose date field falls in this calendar year (e.g. 2025), counted over the WHOLE list, not a page. Ignored if start_date/end_date are given.",
      +  "type": "number"
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotation coverage is already good (readOnly, idempotent, non-destructive, open-world), and the description adds substantive behavior beyond that: the keyless source, the fact that counts span the whole 13,000+ row list rather than a page, the capture date of this copy, and a warning that the counted field is excluded_since/HHSC's StartDate and never added_date. Those are exactly the operational details an agent needs and that annotations cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded in the first sentence, but the text is long, hyphen-heavy, and crams two distinct modes plus sourcing caveats into a dense paragraph. A shorter split into 'summary mode' and 'count mode' would earn the same information with less parsing effort.

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?

For a three-optional-parameter read-only tool with no output schema, the description covers everything an agent needs: what data is described, freshness signals, what the count mode returns, which date field is used, and provenance. Nothing essential is left for the agent to guess.

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 would be 3, but the description adds real meaning: it explains the precedence rule (start_date/end_date override year), confirms counting is over the full list not a page, and identifies which underlying date field is aggregated — a semantic the schema does not reveal. It reinforces but does not exceed what the schema already says about YYYY-MM-DD formatting.

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 the specific resource (Texas HHSC OIG Medicaid Provider Exclusions data) and clearly delineates two modes: a coverage/currency summary and an optional count-by-year-or-range mode, with a concrete example question ('how many Texas HHSC OIG exclusions took effect in 2025'). It stops short of explicitly naming the sibling tx_medical_check_exclusion as the alternative, so the differentiation is implied rather than stated.

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?

It gives a clear use case ('check the screening data is fresh enough to rely on before a compliance decision'), which tells the agent exactly when this tool belongs in a workflow. It does not explicitly state when NOT to use it or name the sibling check tool as the alternative.

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.