Skip to main content
Glama

Get benefit program details

get_program_details
Read-only

Full public details for one program by its id (ids come from find_programs_by_zip or run_eligibility_scan): description, cited government source, how to apply, documents required, and the apply-guide link on discoverseniorbenefits.com. spoken_summary explains it in a few sentences to read aloud.

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": {
      "program_id": "<program_id>"
    },
    "name": "get_program_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNo2-letter state code; resolves state-specific application channels for federal programs.
program_idYesProgram id, e.g. 'fed.msp.qmb'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful behavior beyond that: it discloses the return payload's nature as "public" data with a "cited government source" and explains that spoken_summary is written to be read aloud in a few sentences, which is meaningful for an agent deciding how to present results. There is no output schema, so this return-shape disclosure is doing real work, though it is not exhaustive.

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?

Two sentences, front-loaded with the core purpose and the id provenance before the field list. The parenthetical about where ids come from is placed efficiently inside the first sentence, and the closing note on spoken_summary earns its place by explaining a field's intent.

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 and only two parameters, the description carries the burden of explaining what returns, and it does enumerate the key fields including the apply-guide link and spoken_summary. The one gap is the optional `state` parameter, which is only covered in the schema; otherwise the definition is sufficient for an agent to invoke and present results correctly.

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 both parameters are already documented in the schema, including the purpose of the optional `state` field for resolving state-specific application channels. The only added meaning is the provenance of program_id (from the two sibling tools); the description is silent on the `state` parameter and adds no format or edge-case detail beyond what the schema provides. Baseline 3 applies.

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+resource ("Full public details for one program by its id") and enumerates exactly what comes back: description, cited government source, how to apply, documents required, apply-guide link, and spoken_summary. It also names the sibling tools that produce the id, making it clearly distinguishable from find_programs_by_zip and run_eligibility_scan, which both return program listings rather than one program's full detail.

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?

"ids come from find_programs_by_zip or run_eligibility_scan" gives explicit routing guidance: this is the second step after a search or scan. It stops short of stating exclusions or edge cases (e.g., what to do with an unknown id), but the sequencing guidance is concrete and actionable.

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