Skip to main content
Glama
magicstack-llp

Government Scheme MCP Server

create_scheme

Create a new government scheme record with eligibility criteria, benefits, and required documents. Returns the created scheme as JSON.

Instructions

Create a new government scheme record. Pass only valid fields; unknown fields are ignored. Returns the created row as JSON.

Args:
    code: Unique code for the scheme
    name: Name of the scheme
    description: Description of the scheme
    department: Department offering the scheme
    category: Program domain (education, health, agriculture, housing, women, child, senior, disability, minority, entrepreneurship, employment, skill, welfare)
    benefit_type: Type of benefit (cash, subsidy, scholarship, loan, insurance, pension, grant, in-kind)
    benifit_details: Detailed description of the benefit structure, payouts, timelines
    terms_and_conditions: Terms and conditions text for the scheme
    scheme_raw_text: Raw, unstructured text of scheme details scraped or provided
    official_website: Official scheme website URL
    application_link: Direct application form/link URL
    url: Official URL for the scheme
    contact: Contact information
    min_age: Minimum age requirement
    max_age: Maximum age requirement
    genders: List of allowed genders (male, female, other)
    income_min: Minimum income requirement
    income_max: Maximum income requirement
    employment_status: List of employment statuses (unemployed, farmer, student, salaried, entrepreneur)
    disabilities: List of applicable disabilities (visual, hearing, mobility, intellectual, multiple, other)
    social_categories: List of social categories (SC, ST, OBC, EWS, GENERAL)
    marital_statuses: List of marital statuses (single, married, divorced, widowed)
    religions: List of applicable religions
    states: List of applicable states/UTs
    districts: List of applicable districts
    urban_rural: List of area types (urban, rural)
    professions: List of applicable professions
    required_documents: List of required documents
    caste_required: Whether caste certificate is required
    domicile_required: Whether domicile certificate is required
    is_active: Whether the scheme is active

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeNo
nameNo
descriptionNo
departmentNo
categoryNo
benefit_typeNo
benifit_detailsNo
terms_and_conditionsNo
scheme_raw_textNo
official_websiteNo
application_linkNo
urlNo
contactNo
min_ageNo
max_ageNo
gendersNo
income_minNo
income_maxNo
employment_statusNo
disabilitiesNo
social_categoriesNo
marital_statusesNo
religionsNo
statesNo
districtsNo
urban_ruralNo
professionsNo
required_documentsNo
caste_requiredNo
domicile_requiredNo
is_activeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that unknown fields are ignored and returns the created row as JSON. However, it lacks details on failure modes, idempotency, or permissions required.

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 key behavior in one sentence, then provides a structured list of parameters with brief descriptions. Though lengthy due to 31 parameters, it is 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 the complexity (31 params, no enum constraints), the description covers basic usage and parameter meanings. However, it does not provide guidance on minimal required fields or uniqueness constraints, leaving some gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but the description lists all 31 parameters with meaningful descriptions (e.g., category lists allowed domains). This fully compensates for the schema's lack of descriptions.

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 'Create a new government scheme record', specifying the action (create) and resource (government scheme record). This distinguishes it from sibling tools like update_scheme, delete_scheme, and read_scheme.

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

Usage Guidelines4/5

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

The purpose implies use for creating new records, which is clear context. However, it does not explicitly state when not to use or suggest alternatives, such as using update_scheme for modifications.

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