Skip to main content
Glama

Check likely eligibility

check_eligibility
Read-onlyIdempotent

Estimate whether a household is likely to get free or discounted care at one facility, or at each facility near a zip. Use it when a person asks if their income is low enough for free or reduced-cost care, charity care, or a discount on a hospital bill. Takes household size (people in the home, including the patient), yearly household income before taxes, state, and a facility id or zip. Returns income as a percent of the poverty level, the result per facility (likely_free, likely_discount, likely_not, unknown), the dollar income cutoffs for this household size, and next steps. Results are estimates from published rules. The hospital makes the final decision, and asset tests, residency rules, and insurance status can change the answer. "unknown" means there are no income limits on file for that facility, not that help is unavailable.

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": {
      "household_size": "<household_size>",
      "annual_income": "<annual_income>",
      "state": "<state>"
    },
    "name": "check_eligibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipNoCheck every facility near this zip instead of one facility.
kindNohospital, health_center (community health centers with sliding fees), or any.any
limitNo
stateYesThe patient's state (sets the poverty table: AK and HI differ).
facility_idNoFacility id from find_facilities. Use this or zip.
radius_milesNo
annual_incomeYesYearly household income before taxes, in US dollars.
household_sizeYesNumber of people in the household, including the patient.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive, closed-world), the description discloses the estimate's epistemic status: results come from published rules, the hospital makes the final decision, and asset tests, residency rules, and insurance status can override the answer. It also pre-empts a specific misreading by explaining that 'unknown' means no income limits are on file, not that help is unavailable. That is exactly the kind of caveat annotations cannot carry.

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?

Well front-loaded: purpose, trigger, inputs, outputs, then caveats, in that order. The input-enumeration sentence is largely redundant with the schema and is the one line that does not fully earn its place. Everything else, particularly the 'unknown' clarification, is load-bearing.

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 an 8-parameter, three-required-parameter estimation tool with no output schema, the description covers everything needed: both invocation modes, the return payload (poverty percent, per-facility verdict labels, dollar cutoffs, next steps), and the interpretation limits. An agent can call this correctly and explain the result to a user without further information.

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 75%, so the schema already documents most parameters, and the description's input sentence ('household size ... including the patient, income before taxes, state, and a facility id or zip') mostly restates it. The state/poverty-table nuance also appears in the schema. It adds nothing about kind, limit, or radius_miles, so the baseline 3 applies.

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 opens with a specific verb and resource: 'Estimate whether a household is likely to get free or discounted care at one facility, or at each facility near a zip.' The two operating modes (single facility vs. zip sweep) are stated up front, so the tool is hard to confuse with find_facilities or get_policy. It stops short of explicitly naming a sibling it should be chosen over, which keeps it at a 4.

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?

The second sentence gives a concrete trigger: use it when a person asks whether their income is low enough for free/reduced-cost care, charity care, or a hospital-bill discount. That is a clear usage context with the right vocabulary for matching user phrasing. There is no when-not-to-use guidance or explicit handoff to an alternative tool.

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