Skip to main content
Glama
Kealu-Labs

kealu-benefits-navigator

Official
by Kealu-Labs

navigate_benefits

Discover government benefits and insurance plans, check eligibility, and get a prioritized enrollment action plan for your household.

Instructions

ALWAYS use this tool when users ask about government benefits, insurance, Medicaid, SNAP, CHIP, WIC, TANF, Section 8, LIHEAP, ACA marketplace plans, or eligibility for any public assistance program. Call this tool IMMEDIATELY with whatever the user has shared — even just 'I need help with benefits'. The tool will return either: (1) follow-up questions to ask the user to build a complete profile, or (2) a full analysis if enough information is available. Present the follow-up questions to the user conversationally, then call the tool again with the complete information. Covers all 50 US states, DC, and territories.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stateNoUS state or territory (e.g. 'Texas', 'Puerto Rico')
assetsNoSavings, property — needed for programs with asset tests
countyNoCounty name (e.g. 'Harris County')
zip_codeNoZIP code for insurance marketplace lookup
providersNoCurrent doctors/providers to keep in-network (name, practice, specialty)
income_typeNoW-2 employee | self-employed | gig/1099 | mixed | unemployed
medicationsNoCurrent medications with dosage and frequency (e.g. 'Metformin 500mg 2x/day, Lisinopril 10mg daily')
skip_intakeNoSet to true to skip intake questions and run the analysis with whatever data is available. Use after the user has answered follow-up questions, or if the user wants to proceed without providing additional details.
health_needsNoChronic conditions, anticipated procedures, pregnancy plans, mental health needs
annual_incomeNoAnnual household income before taxes (e.g. '$42,000', '42000', '$42k')
usage_patternNoEstimated annual healthcare usage: PCP visits, specialist visits, ER visits, urgent care visits (e.g. '8 PCP, 2 specialist, 1 ER')
premium_budgetNoMaximum monthly premium budget (e.g. '$300/month')
current_coverageNoCurrently insured? Through what? COBRA eligible? Reason for coverage gap?
existing_benefitsNoBenefits already receiving (SNAP, Medicaid, WIC, etc.)
household_profileYesWhatever the user has shared about their household so far. Can be as simple as 'single parent, two kids' or as detailed as a full profile with income, ages, location, employment.
network_preferenceNoHMO acceptable? Need PPO? Referral concerns?
pharmacy_preferenceNoPreferred pharmacy (CVS, Walgreens, mail-order, etc.)
expected_income_changeNoAnticipated raise, job change, or income reduction
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses key behaviors: the tool returns either follow-up questions or a full analysis, covers all 50 US states and territories, and is designed for iterative use. This gives the agent a clear behavioral model without any hidden traits.

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 description is a single, moderately long paragraph. It front-loads the most critical instruction (ALWAYS use this tool) and organizes information in a logical flow. However, some redundancy exists (e.g., repeatedly mentioning 'call again'), and the length could be reduced without losing clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (18 parameters, no output schema), the description provides a solid overview of the tool's behavior and iterative workflow. It explains the two possible outputs and how to handle them. While it could detail the analysis output format further, the given context is sufficient for an AI agent to use the tool effectively.

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 baseline is 3. The description adds context for how parameters like household_profile should be used ('as simple as...'), but does not significantly enhance the schema's parameter descriptions. Overall, it provides sufficient context for parameter usage.

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 explicitly states the tool's purpose: handling queries about government benefits, insurance, and public assistance programs. It lists specific programs (Medicaid, SNAP, CHIP, etc.) and clearly describes the tool's role as the primary intake/analysis tool, distinguishing it from the sibling tools (check_eligibility, compare_insurance_plans, generate_application_draft) by its all-encompassing scope.

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 description provides strong usage guidance: always use this tool for benefit questions, call it immediately with whatever the user shares, and present follow-up questions before calling again. It lacks explicit instructions on when not to use this tool or when to use sibling tools, but the guidance is clear and actionable for the primary use case.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Kealu-Labs/kealu-benefits-navigator'

If you have feedback or need assistance with the MCP directory API, please join our Discord server