districtapi-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DISTRICTAPI_KEY | Yes | Your District API key. Get a free API key at https://districtapi.dev. |
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 |
|---|---|
| lookup_district_by_addressA | Find the public school district serving a US street address. Returns the district name, NCES ID, state, enrollment, school count, per-pupil expenditure, and demographic breakdown. Args: address: Full US street address, e.g. "1600 Pennsylvania Ave, Austin, TX" |
| get_districtA | Get full profile for a school district by its NCES LEA ID. Args: nces_id: 7-digit NCES Local Education Agency ID, e.g. "4807380" |
| search_districtsA | Search for school districts by name, optionally filtered by state. Args: name: Full or partial district name, e.g. "Austin" or "Austin ISD" state: Two-letter state code to narrow results, e.g. "TX" (optional) |
| get_district_schoolsA | List all schools in a district. Args: nces_id: 7-digit NCES LEA ID of the district |
| get_schoolA | Get full profile for a school by its NCES school ID. Args: nces_id: 12-digit NCES school ID |
| find_schools_near_addressA | Find public schools within a radius of a US street address. Args: address: Full US street address radius_miles: Search radius in miles (default 5.0, max 25.0) |
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 targets a distinct resource and action: address-to-district, district-by-ID, district-search, schools-in-district, school-by-ID, and schools-near-address. The two address-based tools are clearly differentiated by return type (district vs schools).
All tool names follow a consistent verb_noun pattern with optional qualifiers (by_address, near_address, by ID). Verbs (lookup, get, search, find) are semantically distinct and used appropriately, and snake_case is used throughout.
With 6 tools, the set is well-scoped for a school district information API. Each tool addresses a distinct query need without unnecessary redundancy or bloat.
The domain is read-only lookup, and the set covers all natural entry points: by address, by name, by district ID, and by school ID, plus the ability to list schools within a district or near an address. No critical gaps are evident.