Skip to main content
Glama
openpharma-org

Medicaid MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
medicaid_infoC

Unified tool for Medicaid data operations: access enrollment trends, drug pricing (NADAC), quality measures, and program performance from data.medicaid.gov via Socrata SODA API. Provides state-level aggregates (NOT provider-level like Medicare).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.1/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no ambiguity or overlap between tools, as there are no other tools to compare it against. The tool's purpose is clearly defined as a unified interface for Medicaid data operations.

Naming Consistency5/5

Since there is only one tool, naming consistency is inherently perfect. The tool name 'medicaid_info' follows a clear and consistent pattern, though no pattern can be established across multiple tools.

Tool Count2/5

A single tool for a server named 'Medicaid MCP Server' suggests a very thin surface. While it unifies multiple data operations, the scope of Medicaid data (enrollment, drug pricing, quality measures) likely warrants more granular tools for better agent usability and flexibility.

Completeness2/5

The tool covers multiple aspects (enrollment, pricing, quality) in a unified way, but this approach may lead to gaps in specific operations like filtering, updating, or detailed queries. For a Medicaid data domain, a single tool is likely insufficient for comprehensive coverage, as agents might need more targeted actions.

Maintenance

ActivityInactive
ResponsivenessNo issues