Skip to main content
Glama

Find benefit programs by ZIP code or city

find_programs_by_zip
Read-only

List the federal, state, and county senior-benefit programs that apply where a person lives, from their 5-digit ZIP code or their city and state. Each program includes its cited government source URL, a last-verified date, and an apply-guide link on discoverseniorbenefits.com; spoken_summary is a short version to read aloud. Optionally filter by jurisdiction level or category keyword.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_programs_by_zip"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipNo5-digit US ZIP code (or give city + state).
cityNoCity or town name as the person said it (e.g. 'Eastvale'). Use with state when the ZIP code is not known.
levelNoOnly return programs at this jurisdiction level.
stateNoState for the city: 2-letter code or full name (e.g. 'CA').
categoryNoCase-insensitive keyword matched against each program's category (e.g. 'food', 'property tax', 'utilities').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / city
      Added value: +{
      +  "description": "City or town name as the person said it (e.g. 'Eastvale'). Use with state when the ZIP code is not known.",
      +  "maxLength": 80,
      +  "minLength": 2,
      +  "type": "string"
      +}
    • addedInput schema / properties / state
      Added value: +{
      +  "description": "State for the city: 2-letter code or full name (e.g. 'CA').",
      +  "maxLength": 40,
      +  "minLength": 2,
      +  "type": "string"
      +}
    • changedInput schema / properties / zip / description
      Previous value: -"5-digit US ZIP code."New value: +"5-digit US ZIP code (or give city + state)."
    • removedInput schema / required
      Removed value: -[
      -  "zip"
      -]
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false, and closed-world scope, so safety is covered. The description adds genuinely non-derivable behavioral context: every result carries a cited government source URL, a last-verified date, an apply-guide link, and a spoken_summary field for read-aloud use. It stops short of describing pagination or behavior when nothing matches.

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?

Purpose is front-loaded in the first clause, followed by return-shape context and then filter notes, so an agent can stop reading early if it only needs the intent. The second sentence is dense with a long semicolon chain, but no sentence is filler.

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?

With no output schema, the description correctly spends its space enumerating the fields returned (source URL, verified date, apply link, spoken_summary), which is what the agent would otherwise lack. All five parameters are optional per the schema while the description implies one of ZIP or city+state is needed, though the ambiguity of what happens with zero matches is unaddressed.

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 every parameter already carries its own explanation, including the enum for level and the case-insensitive category keyword. The description mostly restates that filtering is optional by level or category and adds no format or disambiguation detail beyond the schema, so the baseline of 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?

States a specific verb ("List") and resource ("federal, state, and county senior-benefit programs") plus the geographic scoping input (ZIP or city+state), so the agent knows exactly what comes back. It does not explicitly contrast itself with get_program_details or run_eligibility_scan, so sibling differentiation is left to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives the two input paths ("from their 5-digit ZIP code or their city and state") and notes filters are optional, which implies the primary call pattern. It offers no when-not guidance and never names an alternative for looking up a single program's full details or checking personal eligibility, both of which are plausible next steps.

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