Government Scheme MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOV_API_URL | No | Base URL for the government schemes API | http://localhost:3000 |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| healthA | Check server health and API connectivity. Returns JSON with ok/api/error. |
| create_schemeA | Create a new government scheme record. Pass only valid fields; unknown fields are ignored. Returns the created row as JSON. |
| read_schemeA | Fetch a single scheme by numeric ID. |
| update_schemeA | Update a government scheme record by ID. Pass only fields to change. |
| delete_schemeB | Delete a scheme by ID. |
| search_schemesA | Search schemes by user profile/filters. Supports various criteria for eligibility matching. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a distinct purpose: CRUD operations (create, delete, read, update), search with filtering, and health check. No overlap or ambiguity.
Tools follow a verb_noun pattern (e.g., create_scheme, delete_scheme), with 'health' as a simple noun. Minor inconsistency: 'search_schemes' uses plural but is still clear.
Six tools is appropriate for a scheme management server: full CRUD plus search and health check. Not too many, not too few.
Covers all essential operations: create, read, update, delete, and search with eligibility criteria. Health check ensures connectivity. No obvious gaps for the domain.