Skip to main content
Glama

search_inspection_reports

Read-onlyIdempotent

Search the text of Ofsted inspection reports by topic (for example SEND support, bullying, early reading) and return matching passages quoted from the reports, each with the school and a link to the page of the report PDF. Can be limited to schools near a postcode, a local authority, a phase or one 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": {
      "query": "<query>"
    },
    "name": "search_inspection_reports"
  }
}

Input Schema

NameRequiredDescriptionDefault
urnNoOnly this school's reports
limitNoPassages to return, 1 to 25 (default 10)
phaseNoall, nursery, primary, secondary or sixteen_plus (default all)
queryYesWhat to look for, in plain words, such as support for pupils with dyslexia
postcodeNoOnly schools near this postcode
radius_kmNoDistance from the postcode in kilometres, 0.5 to 30 (default 5)
local_authorityNoOnly schools in this local authority (name or code)
include_earlier_reportsNoInclude earlier reports as well as each school's latest

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds genuine value beyond them by disclosing the return shape — quoted passages, each attributed to a school, with a link to the relevant PDF page — which is the key unknown for this tool. It does not mention any coverage caveats (e.g. whether all schools have reports) or pagination, keeping it below 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 waste: the first front-loads what is searched and what comes back, the second lists the scoping options. Nothing is redundant and the most decision-relevant information leads.

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 an 8-parameter read tool with no output schema, the description covers both input scoping and the returned passage format, which is the essential missing piece. Minor gaps remain around result-set behaviour (defaults, whether earlier reports are included by default) that the schema already addresses, so it is nearly complete.

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 coverage is 100%, so every parameter already carries a description including ranges and defaults. The description restates the narrowing options (postcode, local authority, phase, single school via urn) but adds no format or interaction detail beyond the schema, so the baseline 3 applies.

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 and resource ("Search the text of Ofsted inspection reports by topic") and even names the unit of return (quoted passages with school and PDF page link), which distinguishes it from a generic school-data search. It never explicitly contrasts itself with the sibling document-search tools (search_school_documents, search_admissions_documents), so the differentiation is inferred from the report type rather than stated.

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 topic examples (SEND support, bullying, early reading) and the note that results can be narrowed to postcode, local authority, phase or a single school give an agent an implicit sense of when this tool applies. However, there is no explicit when-not guidance and no mention of the sibling document-search tools, so the agent must infer that this is the inspection-report-specific variant.

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