Skip to main content
Glama
magicstack-llp

Government Scheme MCP Server

search_schemes

Find government schemes matching your profile. Filter by age, income, gender, location, and more to discover eligible programs.

Instructions

Search schemes by user profile/filters. Supports various criteria for eligibility matching.

Args:
    q: Text to match in name/description
    age: Age of the user
    income: Income of the user
    gender: Gender (male, female, other)
    employmentStatus: Employment status (unemployed, farmer, student, salaried, entrepreneur)
    disabilities: Disabilities (visual, hearing, mobility, intellectual, multiple, other)
    socialCategories: Social categories (SC, ST, OBC, EWS, GENERAL)
    maritalStatus: Marital status (single, married, divorced, widowed)
    religion: Religion
    state: State/UT name
    district: District name
    urbanRural: Area type (urban, rural)
    profession: Profession
    casteRequired: Whether caste certificate is required
    domicileRequired: Whether domicile certificate is required
    category: Program category
    benefitType: Type of benefit (cash, subsidy, scholarship, loan, insurance, pension, grant, in-kind)
    active: Whether to only include active schemes
    limit: Maximum number of results (default: 100)
    offset: Number of results to skip (default: 0)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNo
ageNo
incomeNo
genderNo
employmentStatusNo
disabilitiesNo
socialCategoriesNo
maritalStatusNo
religionNo
stateNo
districtNo
urbanRuralNo
professionNo
casteRequiredNo
domicileRequiredNo
categoryNo
benefitTypeNo
activeNo
limitNo
offsetNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations, the description carries full burden. It lists many parameters but does not disclose behavioral traits like filtering logic (AND/OR), case sensitivity, default sorting, or performance considerations. It adequately describes input but lacks deeper behavioral context.

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?

The description is front-loaded with the purpose sentence, followed by a structured list of parameters. It is efficient but slightly long due to 20 entries; overall well-organized.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 20 parameters and no annotations, the description covers input but does not mention output schema, return format, or pagination behavior beyond limit/offset. An output schema exists but is not referenced, leaving some gaps in completeness.

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 description coverage is 0% (no descriptions in schema), so the description compensates by listing all 20 parameters with brief explanations (e.g., 'age: Age of the user'). However, these explanations are minimal and do not include constraints or examples.

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 'Search schemes by user profile/filters' with a specific verb and resource, and mentions eligibility matching, which distinguishes it from sibling tools like create, delete, read, update, and health.

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

Usage Guidelines3/5

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

The description does not explicitly state when to use this tool versus alternatives, but the context of sibling tools (CRUD + health) implies this is the search/filter tool. No explicit when-not or alternative guidance is provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/magicstack-llp/gov-scheme-mcp-py'

If you have feedback or need assistance with the MCP directory API, please join our Discord server