Skip to main content
Glama

State programs and laws

get_state_programs
Read-onlyIdempotent

Get state-level programs and laws that help with hospital bills in one state, with source URLs and quotes. Use it when the patient's hospital has no policy data, when the hospital is for-profit, or when they ask what their state offers. Takes a two-letter state code. Each program has an applies_to field, because a state program may cover only some hospitals.

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": {
      "state": "<state>"
    },
    "name": "get_state_programs"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYesTwo-letter US state code, for example "MA".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and closed-world behavior, so the description only needs to add data-model context. It does: it discloses that results carry source URLs and quotes, and that each program has an applies_to field because state programs may only cover some hospitals — a real interpretation caveat.

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?

Four short sentences, front-loaded with the purpose and followed by the trigger conditions, then the input, then a caveat about applies_to. Only the state-code sentence is redundant against the schema.

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?

For a one-parameter read tool with no output schema, the description adequately sketches the return payload (programs, laws, source URLs, quotes, applies_to). It stops short of describing empty-result behavior for states with no programs, which would be the remaining useful detail.

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 coverage is 100% and the single parameter already documents the two-letter code with an example. The description's 'Takes a two-letter state code' restates the schema without adding format, casing, or validity guidance beyond it.

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 state-level programs and laws that help with hospital bills') and bounds the scope to a single state, plus states the payload includes source URLs and quotes. An agent can distinguish this from hospital-level policy tools without opening the schema.

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 three concrete trigger conditions: when the hospital has no policy data, when the hospital is for-profit, or when the user asks what their state offers. That is strong positive routing guidance, though it names no fallback tool or explicit 'not for X' exclusion.

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