NCES Education Data

get_schools

Search schools with enrollment, Title I status, type (charter/magnet/regular), and teacher counts.

Returns school directory information from the Common Core of Data (CCD),
including school name, location, enrollment, charter/magnet status,
Title I participation, and full-time equivalent teacher counts.

Args:
    state: Two-letter US state abbreviation (e.g. 'CA', 'NY').
    county_fips: Optional 5-digit county FIPS code to filter by county.
    title_i_only: If True, return only Title I eligible schools.
    year: School year to query (default 2022).
    limit: Maximum number of schools to return (default 50, max 500).

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedApr 3, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden. It discloses the data source (Common Core of Data), the types of information returned, and the filtering options. It does not mention potential side effects or limitations, but for a read-only search tool, this is adequate and adds valuable context beyond the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured: a concise summary sentence, a brief elaboration on return details, and a clear Args list. No unnecessary repetition; every sentence adds value.

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

Completeness5/5

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

Despite having an output schema, the description still provides a clear picture of what data is returned. All 5 parameters are explained, including defaults and constraints. For a search tool with this complexity, the description is complete and self-sufficient.

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 description coverage is 0%, and the description fully compensates with a detailed Args section explaining each parameter, including examples for state, the 5-digit format for county_fips, the meaning of title_i_only, and default/max values for year and limit. This goes well beyond the bare schema.

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 a specific verb ('Search') and resource ('schools'), and lists the specific data fields (enrollment, Title I status, type, teacher counts) that distinguish it from sibling tools focusing on finance, graduation rates, and demographics.

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 implies usage by defining what the tool returns, but it does not explicitly state when to use it vs. alternatives or provide any exclusions. The sibling tool names suggest context, but the description itself lacks direct guidance.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?