Skip to main content
Glama
Sign In

NYC School Ratings

by io.github.biserd
OverviewDiscussionsAdmin

compare_schools

Read-only

Compare two to four distinct canonical school DBNs on identically defined available metrics, programs, and separate 2026 survey instruments. Includes demographics, enrollment history and same-year, same-exam Regents comparisons with reporting years and source links. Missing values remain null and early-childhood providers are not assigned K–12 scores.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "dbns": "<dbns>"
    },
    "name": "compare_schools"
  }
}

Input Schema

NameRequiredDescriptionDefault
dbnsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare this a safe, read-only, closed-world operation, and the description adds real substance on top: null handling for missing values, the exclusion of early-childhood providers from K-12 scores, and the guarantee that metrics are identically defined and Regents results are same-year, same-exam with reporting years and source links.

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?

Three front-loaded sentences that are dense with substance; the scope and comparison basis come first, followed by included content and edge-case rules. Slightly packed, but no sentence is filler.

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?

With no output schema, the description supplies the return content (demographics, enrollment history, Regents comparisons with reporting years and source links) and the null semantics for missing data, so an agent knows both what goes in and roughly what comes back.

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 description coverage is 0%, so the description carries the burden, and it does clarify that the DBNs must be canonical and distinct and that the count spans two to four, matching the minItems/maxItems constraints. Format details such as the pattern are left to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Compare') and resource ('canonical school DBNs') with an explicit cardinality bound of two to four. It is clearly a multi-school comparison rather than a lookup, which separates it in spirit from search_schools and get_school_details, though no sibling is named outright.

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?

Usage is implied by the comparison framing and the 2-4 school bound, but there is no explicit when-to-use or when-not-to-use guidance, and no mention of the sibling tools an agent should prefer for searching or for a single school's full profile.

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

All NYC School Ratings toolsInspect
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