Skip to main content
Glama

How to apply for financial assistance

get_application_steps
Read-onlyIdempotent

Get how to apply for financial assistance at one facility: application link, deadline, documents to gather, financial counseling phone, and the plain-language summary link. Use it after check_eligibility shows likely_free, likely_discount, or unknown, or whenever the patient asks how to apply. Takes the facility id from find_facilities. Returns the application fields, the data tier, any state program, and a list of steps. Null fields mean the value is not on file.

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_application_steps"
  }
}

Input Schema

NameRequiredDescriptionDefault
facility_idYesHospital CCN, facility slug, or health center org id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds real value by disclosing the return composition (application fields, data tier, state program, step list) and, importantly, that null fields mean the value is not on file — a semantic detail annotations cannot convey. It omits nothing critical for a read-only lookup, though it could mention pagination or absence of coverage for some facilities.

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?

Three sentences: what it returns, when to call it, and what comes back. The payload list is front-loaded and the null-field caveat is placed exactly where it matters. No redundant restatement of the title or annotations.

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 one required parameter, no output schema, and otherwise thin structured metadata, the description carries its share: it explains both what goes in, where to get it, what comes out, and how to read null values. Nothing an agent needs to invoke this correctly is missing.

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% and already lists the accepted identifier forms (hospital CCN, facility slug, health center org id), so the baseline would be 3. The description adds provenance guidance — take the id from find_facilities — which meaningfully helps the agent source a valid value rather than guess a format.

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 opening sentence names a specific verb ('Get how to apply') and resource (financial assistance application for one facility), then enumerates the concrete payload: application link, deadline, documents, counseling phone, summary link. This is clearly distinguishable from siblings like check_eligibility and get_policy.

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?

It gives explicit triggering conditions: use after check_eligibility returns likely_free, likely_discount, or unknown, or when the patient asks how to apply. It also states the input dependency ('Takes the facility id from find_facilities'), creating a clear call sequence rather than leaving ordering to inference.

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