Skip to main content
Glama

find_schools

Read-onlyIdempotent

Find schools near a postcode, town, city or district in England or Wales (Northern Ireland postcodes are not loaded). Returns each school's phase, type, distance, latest Ofsted outcome and headline results compared with similar schools, with a link to its page.

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": {
      "location": "<location>"
    },
    "name": "find_schools"
  }
}

Input Schema

NameRequiredDescriptionDefault
faithNoall, faith or no_faith (default all)
limitNoMost schools to return, nearest first, 1 to 100 (default 25)
phaseNoall, nursery, primary, secondary or sixteen_plus (default all)
genderNoall, mixed, girls or boys (default all)
locationYesA UK postcode such as SW1A 1AA, or a town, city or district in England such as Harrogate
radius_kmNoSearch radius in kilometres, 0.5 to 25 (default 3)
admissionsNoall, selective (grammar schools) or non_selective (default all)
school_typeNoall, state, academy, la_maintained, special or independent (default all)
sen_provisionNoOnly schools with an SEN unit or resourced provision
exclude_concernNoLeave out schools Ofsted has placed in a category of concern

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, non-open-world behavior, so safety is covered. The description adds genuinely non-obvious context beyond that: the dataset's coverage gap for Northern Ireland postcodes, and that results include distance plus headline results benchmarked against similar schools. It does not mention pagination or result-count behavior, keeping it short of a 5.

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?

Two sentences, zero padding, with the location scope and the coverage caveat front-loaded before the return-value summary. Every clause carries information an agent would otherwise have to guess.

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 10-parameter search with no output schema, the description does the important work of enumerating return fields and flagging the Northern Ireland data gap. Minor gaps remain around ordering beyond "nearest first" and truncation when limit is hit, but nothing essential to calling it correctly is missing.

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%, so all ten filters (faith, phase, gender, admissions, school_type, sen_provision, exclude_concern, radius_km, limit) are already documented with defaults and ranges. The description only reinforces the semantics of the required location parameter and adds nothing about filtering interactions or radius/limit behavior, so the baseline of 3 applies.

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 gives a specific verb and resource ("Find schools near a postcode, town, city or district"), bounds the geography to England and Wales, and explicitly excludes a case ("Northern Ireland postcodes are not loaded"). It also names what comes back (phase, type, distance, Ofsted outcome, results comparison, link), so an agent can separate it from name-based or ranking siblings without opening the schema.

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?

The framing "near a postcode, town, city or district" implies proximity/geographic search, and the Northern Ireland exclusion is a real usage boundary. However, no sibling is named as an alternative and there is no explicit when-not guidance (e.g., use search_schools_by_name when you already know the name, or compare_schools for direct comparison).

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