Skip to main content
Glama

Find a public school

find_school
Read-onlyIdempotent

Finds NSW public schools that have an intake zone, by name, with the four-digit codes find_homes takes in profile.schools.zoneSchools.

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": {
      "text": "<text>"
    },
    "name": "find_school"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesWhat the buyer called it: at least a couple of letters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so safety is covered. The description adds real behavior beyond them: only schools with an intake zone are returned, so absence of a result may mean "no zone" rather than "no such school", and the output is a four-digit code. It does not say what happens on zero matches or whether multiple schools can be returned for one name.

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?

A single sentence with no filler, front-loading the resource and its constraint before the downstream usage note. The trailing clause about profile.schools.zoneSchools is dense but earns its place by tying the output to a sibling tool.

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?

For a one-parameter lookup with no output schema, the description supplies the key missing piece: the return value is a four-digit zone school code consumed by find_homes. Only edge-case behavior (no match, multiple matches) is unaddressed, which is a minor gap at this complexity level.

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

Parameters3/5

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

Schema description coverage is 100% and the single parameter already documents itself as "What the buyer called it: at least a couple of letters". The description's "by name" adds little beyond that, and it gives no detail on matching behavior (partial vs exact, case handling) that the schema does not cover.

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?

States a specific verb and resource ("Finds NSW public schools") plus two scoping qualifiers: results are limited to schools that have an intake zone, and lookup is by name. It also names the downstream consumer (find_homes) and the exact field the returned four-digit codes populate, so an agent can distinguish this from find_place/find_suburb 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?

Usage context is clear: call this when you need zone school codes to feed profile.schools.zoneSchools in find_homes. That is a genuine routing signal. It stops short of explicit exclusions, though — it never says to use find_place or find_suburb for non-school lookups, so the agent must infer the boundary.

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