Skip to main content
Glama

search_admissions_documents

Read-onlyIdempotent

Search council school admissions documents (admissions booklets, allocation figures, oversubscription criteria) by topic, such as sibling priority, feeder schools or how distance is measured. Returns passages with a link to the council's document. Can be limited to one local authority.

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

Input Schema

NameRequiredDescriptionDefault
limitNoPassages to return, 1 to 25 (default 10)
queryYesWhat to look for, such as sibling priority or how distance is measured
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
local_authorityNoOnly this council's documents (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 safety is covered. The description adds genuinely new context by disclosing the return shape ('passages with a link to the council's document') and the scoping behavior of restricting to a single council, which matters 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?

Three sentences, front-loaded with the action and resource, followed by return shape and scope. The parenthetical document list is dense but earns its place by disambiguating the corpus; no filler or repetition.

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 read-only search tool with full schema coverage and no output schema, the description supplies what is missing: the corpus scope, the topical query model, and the shape of the results including source links. It does not explain the answer parameter's fallback behavior, but the schema already covers that.

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 four parameters are already documented in structured form, and the baseline is 3. The description only echoes the query-as-topic idea and the local-authority scoping; it adds nothing about the limit range or the citation-style behavior of the answer parameter beyond what the schema states.

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 gives a specific verb and resource ('Search council school admissions documents') and enumerates the document types covered (admissions booklets, allocation figures, oversubscription criteria). It stops short of distinguishing this tool from the sibling search_school_documents or search_inspection_reports, so an agent must infer the boundary from the resource noun alone.

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 implied by the topic examples ('sibling priority, feeder schools or how distance is measured') and by the note that results can be limited to one local authority, which signals the intended query pattern. There is no explicit statement of when to prefer this over the other search tools, nor any exclusion or prerequisite.

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