NCES Education Data

get_district_overview

Get district directory overview: district name, student count, school count, teachers, locale type.

Returns district-level summary information from the CCD District Directory,
including total enrollment, number of schools, teacher FTE counts,
and urban/suburban/rural locale classification.

Args:
    state: Two-letter US state abbreviation (e.g. 'CA', 'NY').
    year: School year to query (default 2022).
    limit: Maximum number of districts to return (default 50, max 500).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`year`	No
`limit`	No
`state`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the burden and does well by disclosing the data source (CCD District Directory), the nature of the output (district summary metrics), and the limit cap of 500. It implies a read-only operation through 'Get' and 'Returns', but does not explicitly discuss authentication, rate limits, or error conditions.

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 well-structured with a summary line, a detailed sentence, and an Args list. However, there is slight redundancy between the opening overview fields and the later detailed field list (e.g., 'student count' vs 'total enrollment').

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

Completeness4/5

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

Given the presence of an output schema and only three parameters, the description is nearly complete: it covers the data source, output fields, and parameter semantics. It lacks explicit usage guidance relative to sibling tools, but that's a minor gap for a straightforward lookup operation.

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?

Since schema coverage is 0%, the description fully compensates by adding meaning to all three parameters: state format with examples, year default, and limit default with maximum (500). This is more detailed than the bare schema properties.

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 uses a specific verb ('Get') and clearly specifies the resource ('district directory overview') and the fields returned (district name, student count, school count, teachers, locale type). This clearly differentiates it from sibling tools like get_district_finance or get_graduation_rates.

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 intended use is implied by the description of returning district-level summary information from the CCD District Directory, but there is no explicit statement about when to use this tool versus alternatives like finance or demographics tools. No exclusions or alternative guidance are provided.

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

All NCES Education Data tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

Each tool targets a distinct data type: finance, directory overview, graduation rates, demographics, and school directory. Although some tools overlap in attributes (e.g., enrollment in get_schools and get_school_demographics), the level of detail and purpose are clearly separated.

Naming Consistency5/5

All tool names follow a consistent 'get_' prefix and snake_case convention, with predictable patterns like get_district_finance and get_school_demographics. This makes the set easy to navigate.

Tool Count5/5

The server has 5 tools, which is well within the ideal range for a focused data retrieval domain. Each tool covers a meaningful aspect of NCES education data without being redundant or overwhelming.

Completeness4/5

The set covers key K-12 data categories: finance, demographics, graduation, and directory information. Minor gaps (e.g., district-level demographics, state-level aggregates, or test scores) exist, but the core data types are well represented and there are no dead ends.

Resources

Need Help?