Skip to main content
Glama

find_send_support

Read-onlyIdempotent

Find state primary or secondary schools near a postcode in England with what is published about special educational needs and disabilities (SEND) at each: an SEN unit or resourced provision, the share of pupils on SEN support and with an EHC plan against the England median, the Parent View answer from parents of children with SEND, and a quote about SEND from the latest Ofsted inspection report with a link. Also gives the council's record on issuing EHC plans within 20 weeks and its latest area SEND inspection.

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": {
      "postcode": "<postcode>"
    },
    "name": "find_send_support"
  }
}

Input Schema

NameRequiredDescriptionDefault
phaseNoprimary or secondary (default primary)
postcodeYesA postcode in England
radius_kmNoSearch radius in km, 0.5 to 15 (default 3)
sen_provisionNoOnly schools with an SEN unit or resourced provision

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 openWorldHint=false, so the safety profile is covered structurally. The description adds useful domain context — England-only scope, median benchmarking, Ofsted quote with link — but omits result limits (how many schools are returned), ordering, and behavior for invalid or out-of-England postcodes. With no output schema, a bit more on result shape would have earned a 4.

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?

The verb and the location constraint are front-loaded, and every clause names concrete data the caller receives rather than filler. The first sentence is long and heavily comma-laden, which slightly hurts scanability, but there is no redundant restatement of the name or schema.

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?

With no output schema, the description carries the burden of explaining return values and does so thoroughly — per-school SEND metrics, a Parent View answer, an inspection quote with link, plus council-level EHC-plan and area SEND inspection context. Remaining gaps (result count, pagination, failure modes for bad postcodes) are modest for a read-only lookup tool.

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 the baseline is 3; phase, postcode, radius_km and sen_provision all carry their own descriptions including defaults and bounds. The description adds only marginal meaning, notably that results are state schools in England, without clarifying radius behavior or how sen_provision interacts with phase.

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?

The description uses a specific verb ('Find') with a well-qualified resource: state primary or secondary schools near a postcode in England, scoped to SEND data. The enumeration of returned signals (SEN unit/resourced provision, SEN support share vs England median, Parent View, Ofsted quote, council EHC-plan timeliness) makes the SEND focus unmistakable, implicitly separating it from generic siblings like find_schools. It stops short of naming a sibling to contrast with, so it is not a 5.

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 only implied: an agent can infer this is the tool for SEND-related school discovery near a postcode. There is no explicit when-to-use vs when-not, no mention of alternatives such as find_schools or compare_schools, and no stated preconditions beyond England coverage.

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