California Assisted Living Waiver MCP server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_program_summaryA | Return statewide enrollment, statewide waitlist, participating provider-record count, county coverage, licensed PEU capacity, sources, dates, license, and interpretation cautions. |
| list_countiesA | List all 15 counties with participating ALW facilities, including provider-record counts and licensed PEU capacity. Does not fabricate county waitlist values. |
| get_county_summaryA | Return participating provider-record count, licensed capacity, median record capacity, and the five largest provider records for one California ALW county. |
| search_facilitiesA | Search public DHCS participating-provider records by name/address text, county, city, or ZIP. Returns at most 50 records and does not imply current vacancy. |
| get_methodology_and_citationA | Return provenance, normalization method, limitations, license, suggested citation, canonical tracker, and publisher business disclosure. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| compare_alw_counties | Create a careful comparison prompt that avoids treating licensed capacity as vacancy or the statewide waitlist as county data. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| methodology | Provenance, limitations, licensing, and citation guidance. |
| county-summaries | All 15 participating counties with facility counts and capacity. |
TDQS
Scored across 5 tools
Each tool targets a distinct concern: program-level stats, county listing, county details, facility search, and methodology. The two county tools (list_counties vs get_county_summary) are related but list_counties aggregates all counties while get_county_summary drills into one, and their descriptions clarify the distinction. Overall clear separation.
Tools generally follow verb_noun pattern (get_program_summary, list_counties, get_county_summary, search_facilities, get_methodology_and_citation), all using snake_case with descriptive verbs. Minor inconsistency: get_methodology_and_citation is longer and compounds two nouns, but the naming is otherwise consistent and readable.
Five tools is a reasonable, focused surface for a domain-specific reference server. The scope is narrow (a single waiver program), so five tools are neither sparse nor bloated. Slightly on the lean side but appropriate for the read-only data-provider purpose.
The surface covers program overview, county-level navigation, facility search, and methodology/citation—a coherent read-only reference workflow with no dead ends. Minor gaps exist (e.g., no tool for provider-level detail beyond the top-five, no county-to-facility cross-filtering), but agents can accomplish core lookup tasks fully.