Skip to main content
Glama

Motley NYC — Neighborhoods, Schools & Admissions

get-zoned-school

Read-onlyIdempotent

Use this when a family asks which elementary school is zoned for a specific NYC address, such as an apartment or building they name. NYC draws school zones building by building, so pass the street address exactly as they typed it — building number and street, ideally with the borough — never the device's location. Returns the zoned K-5 school, the neighborhood, and how zoned admission works; some areas, like all of District 1, have no zoned school.

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": {
      "address": "<address>"
    },
    "name": "get-zoned-school"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesThe NYC street address to look up, as the family typed it, with the building number and ideally the borough — e.g. "123 7th Ave, Brooklyn". A zone line can run between two buildings on one block, so a city or neighborhood can't answer this; never the device's location.

Output Schema

NameRequiredDescriptionDefault
noteNo
foundYes
queryYes
reasonNo
messageNo
candidatesNo
neighborhoodNo
zoned_schoolNo
matched_addressYes
also_zoned_schoolsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / also_zoned_schools
      Added value: +{
      +  "items": {
      +    "$ref": "#/properties/zoned_school"
      +  },
      +  "type": "array"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / address / description
      Previous value: -"The street address of a home the family lives in or is considering, with the building number and ideally the borough — e.g. \"123 7th Ave, Brooklyn\". Only an address the family gave you; never the device's location."New value: +"The NYC street address to look up, as the family typed it, with the building number and ideally the borough — e.g. \"123 7th Ave, Brooklyn\". A zone line can run between two buildings on one block, so a city or neighborhood can't answer this; never the device's location."
  3. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered; the description adds substantive context they cannot: what comes back (zoned K-5 school, neighborhood, how zoned admission works) and an important edge case that all of District 1 has no zoned school. That no-result case is exactly the behavior an agent would otherwise misread as a failure.

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?

Three sentences, front-loaded with the triggering situation, then the input constraint, then the return shape and the no-zone caveat. Every sentence carries distinct information; there is no padding.

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?

For a single-parameter lookup with annotations and an output schema, this covers everything an agent needs: when to call it, how to form the address, what it returns, and the no-zoned-school outcome. Return-value detail is correctly delegated to the output schema.

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, but the description supplies the rationale the schema only asserts: zones are drawn building by building, so the address must be passed as the family typed it with building number and borough. That 'why' helps the agent resist normalizing or substituting a city name.

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?

Names a specific verb+resource ('which elementary school is zoned for a specific NYC address') and scopes it to NYC zoning, which cleanly separates it from generic siblings like find-school and browse-schools. An agent can route a zoning question here without opening any schema.

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?

"Use this when a family asks which elementary school is zoned for a specific NYC address" gives a clear triggering condition, plus a concrete exclusion ('never the device's location' and 'a city or neighborhood can't answer this'). It stops short of naming a sibling alternative for non-zoned school lookups, so routing against find-school is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources