Skip to main content
Glama

Find schools near new homes

find_schools
Read-onlyIdempotent

Use this for schools near the new homes for sale in a place: by phase (primary or secondary), Ofsted grade (Outstanding, or good or better), grammar schools and single-sex schools. Each school comes with its Ofsted judgement and date, how many new homes for sale are near it, and its nearest developments; by council groups them for "where are the grammar schools". The schools nearest one home are among the area facts of that home. England only.

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

Input Schema

NameRequiredDescriptionDefault
byNoschool
gradeNoany
phaseNo
placeYesA town, county or council area.
singleNo
grammarNoGrammar schools only: secondaries that select by ability.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so safety is covered. The description adds genuinely non-schema information: what each result carries (Ofsted judgement and date, count of new homes near it, nearest developments) and the council grouping behavior. It does not mention result limits, ordering, or pagination, which is the main remaining gap given there is no output schema.

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?

Front-loaded with the use case, then packs filters and return contents into two dense sentences, ending with the critical 'England only' scope flag. Slightly heavy listing style ('by phase..., Ofsted grade..., grammar schools and single-sex schools') and repeated 'new homes for sale' phrasing, but no sentence is wasteful.

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?

Six parameters with no output schema, so the description must explain returns - and it does, naming the Ofsted data, nearby-home counts, nearest developments, and grouping. Combined with the England-only constraint and the area_facts cross-reference, an agent has enough to call it correctly. Missing only volume/ordering expectations for the result set.

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 only 33% (only place and grammar are documented in-schema), so the description carries real weight: it maps the phase filter to primary/secondary, clarifies 'good or better' as the Ofsted grade option including Outstanding, explains that 'single' means single-sex schools, and explains what by=council does. It does not spell out the by=school default or the meaning of grade=any, leaving a small ambiguity.

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-like use ('Use this for schools near the new homes for sale in a place') plus the resources returned (schools with Ofsted judgement/date, nearby new-home counts, nearest developments). It clearly carves out a schools-lookup capability that none of the listed siblings occupy. It stops short of naming a sibling it must be distinguished from, which keeps it at 4 rather than 5.

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?

Gives clear context for when to call it (schools near new homes in a place, England only) and implicitly routes single-home lookups away by noting 'The schools nearest one home are among the area facts of that home.' It also flags the specific use case for by=council ('where are the grammar schools'). It never states exclusions or prerequisites beyond the England-only scope note, so no 5.

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