Skip to main content
Glama
Sign In

Medicaid Intelligence

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Medicaid Monthly Managed Care

medicaid_monthly_managed_care
Read-onlyIdempotent

Show monthly Medicaid/CHIP enrollment for one state and managed-care participation category. Data-quality flags and confidentiality suppression are preserved.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "state": "California",
      "to_month": "202212",
      "from_month": "202201",
      "participation": "Comprehensive managed care"
    },
    "name": "medicaid_monthly_managed_care"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYesUS state, as a two-letter code ("CA") or a full name ("California") — both are accepted.
to_monthNoYYYYMM.
from_monthNoYYYYMM.
participationYesExact CMS category, e.g. "Comprehensive managed care".

Output Schema

NameRequiredDescriptionDefault
totalYes
monthsYes
sourceYes
returnedYes
interpretationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare readOnlyHint true, openWorldHint true, idempotentHint true, and destructiveHint false. The description adds a meaningful behavioral detail: 'Data-quality flags and confidentiality suppression are preserved,' which informs the agent that the output may include flags or suppressed data, going beyond the safety profile indicated by annotations.

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?

The description is two sentences, front-loaded with the primary purpose, followed by a brief note on data-quality preservation. Every sentence earns its place with no extraneous content.

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 presence of an output schema and comprehensive annotations, the description provides sufficient context. It covers the tool's scope (single state, participation category), its read-only nature via annotations, and the data-quality/suppression behavior. It does not mention optional time-range parameters, but the schema already documents those.

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%, with all four parameters described (state, to_month, from_month, participation). The description adds no further parameter-level detail beyond restating the state and participation scope, so it remains at the baseline expected for fully covered schemas.

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 clearly states the tool shows monthly Medicaid/CHIP enrollment for a single state and a managed-care participation category, using a specific verb ('Show') and resource ('monthly enrollment'). It distinguishes from sibling tools by explicitly scoping to 'one state' and a specific 'participation category', which differentiates it from summary-level or trend-focused siblings.

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

Usage Guidelines2/5

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

The description provides no explicit guidance on when to use this tool versus the sibling Medicaid managed care tools, no mention of alternatives, and no exclusion criteria. It only states what it does, leaving usage decisions entirely to the agent without actionable context.

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

All Medicaid Intelligence toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources