NCES Education Data

get_graduation_rates

Get 4-year adjusted cohort graduation rates by school.

Returns graduation rate data from EdFacts, including cohort counts
and midpoint graduation rates. Filterable by state or county.

Args:
    state: Two-letter US state abbreviation (e.g. 'CA', 'NY').
    county_fips: Optional 5-digit county FIPS code to filter by county.
    year: School year to query (default 2021). Graduation data may lag.
    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

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations, the description carries full burden. It discloses that data comes from EdFacts, includes cohort counts and midpoint rates, and notes that graduation data may lag. It also mentions state is required and county is optional. However, it doesn't describe response structure or pagination, though an output schema exists.

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 concise and well-structured: a one-sentence purpose, a sentence on return data, and a clearly formatted Args list. Every sentence adds value with no redundancy.

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?

The description is largely complete for a read-only tool with an output schema. It includes purpose, parameters, data source, and a data freshness caveat. The only minor gap is that 'Filterable by state or county' implies state is optional, but state is required; also, there's no explicit guidance on alternatives, but that's more under usage guidelines. The output schema covers return values.

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?

The schema provides only titles and defaults with no descriptions (0% coverage). The description's Args section adds substantial meaning: state is a two-letter abbreviation, county_fips is a 5-digit code, year defaults to 2021 with a lag caveat, and limit has default and max values. This fully compensates for the schema's lack of detail.

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 it retrieves 4-year adjusted cohort graduation rates by school, which is a specific verb and resource. This distinguishes it from sibling tools like get_district_finance or get_school_demographics. The addition of data source (EdFacts) and return contents (cohort counts, midpoint graduation rates) further clarifies its purpose.

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 description implies when to use: whenever graduation rate data is needed. It provides filtering by state or county, but does not explicitly mention alternatives or exclusions. While it doesn't name sibling tools, the context is clear enough for an agent to select it for graduation-related queries.

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?