Skip to main content
Glama
LizzleChen

local-dfw-mcp

by LizzleChen

dfw_tea_schools

Read-onlyIdempotent

Search Texas public schools by campus, district, or county to retrieve TEA A-F accountability ratings, sub-scores, enrollment, and demographics.

Instructions

Texas public schools + TEA A-F accountability ratings (latest published: 2022-2023). Search by campus name, district, or county (e.g. DALLAS, TARRANT, COLLIN, DENTON). Returns overall rating, sub-scores (Student Achievement, School Progress, Closing the Gaps), enrollment, and demographics. Does NOT map an address to its assigned schools — attendance zones are managed by individual ISDs. Source: Texas Education Agency.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (default 25).
campusNoCampus name, contains-match. Example: "Booker T Washington", "Frisco HS".
countyNoCounty name. Example: "DALLAS", "TARRANT", "COLLIN", "DENTON".
ratingNoFilter by overall A-F rating.
districtNoDistrict name, contains-match. Example: "Dallas ISD", "Frisco ISD", "Plano".
school_typeNoFilter by campus level.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesNumber of results in this page.
queryNoEcho of the input filters.
offsetNoCurrent page offset for pagination.
resultsYesResult rows.
nextCursorNoOpaque pagination cursor for the next page; null if no more results.
Behavior4/5

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

Beyond annotations (readOnlyHint, idempotentHint), the description adds data freshness (2022-2023), data source (Texas Education Agency), and the specific fields returned (overall rating, sub-scores, enrollment, demographics). It does not contradict annotations. This is good context but could mention pagination or rate limits.

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 (5 sentences) with no waste. It front-loads the main purpose, includes essential caveats, and is well-structured. Every sentence adds value.

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 tool has 6 parameters and an output schema, the description covers the key return fields and limitations. It lacks information on error handling or zero-result scenarios, but with 100% schema coverage and output schema present, it is sufficiently complete for an experienced user.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds value by providing example values for county and campus parameters, and explains the meaning of rating filter. This enhances understanding beyond the schema's basic 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 the tool returns Texas public school accountability ratings from TEA, with specific search criteria. It distinguishes from siblings by focusing on a unique domain (schools vs. crime, health, etc.). The verb 'search' and resource 'schools with ratings' are specific and unambiguous.

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 provides clear search categories (campus, district, county) and explicitly states what the tool does NOT do (address-to-school mapping). It includes examples for county values. However, it could explicitly contrast with sibling tools, though that is not necessary given different domains.

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/LizzleChen/local-dfw-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server