Skip to main content
Glama

Get a facility's financial assistance policy

get_policy
Read-onlyIdempotent

Get the full financial assistance (charity care) policy we hold for one hospital or health center, with source URLs, short quotes, and last-checked date. Use it when the patient asks what the policy says, or to get the source behind a policy fact. Takes the facility id from find_facilities (hospital CCN, slug, or health center id). Returns the data tier (verified, IRS filing with tax year, state program, or legal baseline only), the thresholds used, the policy with sources, IRS filing details, and state programs. Null fields mean the value is not known.

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": {
      "facility_id": "<facility_id>"
    },
    "name": "get_policy"
  }
}

Input Schema

NameRequiredDescriptionDefault
facility_idYesHospital CCN (for example "220071"), facility slug, or health center org id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, closed-world behavior, and the description goes well beyond them: it enumerates the returned data tiers (verified, IRS filing with tax year, state program, legal baseline only), the thresholds, sources, last-checked date, and crucially explains that null fields mean the value is unknown. That null-semantics note is the kind of interpretive detail 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.

Conciseness5/5

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

Roughly four sentences, each front-loaded with a distinct payload: what it returns, when to call it, where the id comes from, and what comes back. There is no filler or repetition, and the ordering follows the agent's decision sequence.

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 thoroughly — data tier, thresholds, policy sources, IRS filing details, state programs — plus the null-value convention and the upstream dependency on find_facilities. Nothing an agent needs to call or interpret this tool is missing.

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 description coverage is 100%, so the accepted id forms (hospital CCN, slug, health center org id) are already documented in the schema, and the description largely restates them. The only added meaning is the provenance hint that the id comes from find_facilities, which is useful but small — baseline 3 is appropriate.

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?

The description opens with a specific verb and resource ('Get the full financial assistance (charity care) policy') and immediately scopes it to 'one hospital or health center', naming the artifacts returned (source URLs, quotes, last-checked date). This is clearly distinguishable from siblings like get_state_programs or check_eligibility, which operate at the program or eligibility level rather than the per-facility policy level.

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 an explicit trigger ('when the patient asks what the policy says') plus a secondary use ('to get the source behind a policy fact'), and states the prerequisite that the facility id comes from find_facilities. It does not state when NOT to use it or contrast with other lookups, so it stops short of full routing guidance.

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