Skip to main content
Glama

search_school_documents

Read-onlyIdempotent

Search documents published on schools' own websites (admissions policies, SEND information reports, pupil premium statements, curriculum and behaviour policies, the length of the school week, term dates and menus) by topic. Returns passages with a link to the school's document. Can be limited to one school, one local authority or one type of document.

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_school_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
urnNoOnly this school's documents
limitNoPassages to return, 1 to 25 (default 10)
queryYesWhat to look for, such as sibling priority, reading scheme or school day
answerNoAlso return a generated summary of the top passages in which every sentence cites a passage by its position (1 is the first). Left out when the site has no answer model or the summary fails its checks
doc_typeNoOne of admissions_policy, send_report, pupil_premium, curriculum, behaviour, school_week, term_dates, menu
local_authorityNoOnly schools in this council (name or code)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/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. The description adds value the annotations do not: the return shape ('passages with a link to the school's document') and the conditional behavior of the answer flag ('left out when the site has no answer model or the summary fails its checks'), which tells the agent the field may legitimately be absent.

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?

Two sentences, front-loaded with the corpus definition before the return behavior and scoping. The parenthetical document list is long and partly duplicates the doc_type enum values, but each item still helps the agent map a topic to the right corpus, so the length is mostly earned.

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 appropriately covers what comes back (passages plus a link) and the answer-flag caveat. For a 6-parameter, well-documented search tool this is close to complete; it omits only passage-level detail such as length or ordering, which is not critical for correct invocation.

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%, with the limit range, doc_type values, urn meaning and local_authority formats all documented inline, so the baseline is 3. The description only restates the scoping capability ('one school, one local authority or one type of document') without adding syntax, defaults, or interaction rules beyond the schema.

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 documents published on schools' own websites') and enumerates the document classes covered, so the agent knows what corpus is behind it. It does not differentiate itself from the sibling search_admissions_documents, whose domain (admissions) overlaps with the admissions_policy doc_type listed here, so the boundary is left to inference.

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 final sentence gives scoping guidance ('Can be limited to one school, one local authority or one type of document'), which is effectively usage advice about narrowing. However, there is no when-to-use versus alternatives statement and no exclusions, so the agent must infer that this is the broad/general document search rather than the admissions-specific one.

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