Skip to main content
Glama

search_schools_by_name

Read-onlyIdempotent

Look up schools in England and Wales by name. Returns each match's key (the URN, or for Northern Ireland the DE reference number; used by get_school), town, postcode and page link.

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

Input Schema

NameRequiredDescriptionDefault
nameYesAll or part of a school's name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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. The description adds real value by enumerating the return fields (URN/DE reference, town, postcode, page link) and flagging that the key feeds get_school, but it does not say what happens with zero matches or how results are ordered/paged beyond the "page link" hint.

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 scope and followed by the return shape — nothing is redundant. The parenthetical defining the key spans two jurisdictions and is dense enough to slow reading, which keeps it from a 5.

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 one-parameter, no-output-schema search tool, the description covers purpose, return fields, and downstream usage well. The remaining gap is edge-case behavior (no results, result limits), which is minor here but would matter to an agent composing a search-then-fetch flow.

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% and the single parameter is already documented as "All or part of a school's name". The description's "by name" and "each match" reinforce partial-match/multi-result behavior but add no format, casing, or length guidance 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 — "Look up schools ... by name" — so the agent knows exactly what it retrieves. It does not distinguish itself from the sibling find_schools, and the geography statement ("England and Wales") is slightly at odds with the later mention of a Northern Ireland DE reference number, though that detail is informative rather than misleading.

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?

Implicit guidance only: the description indicates the returned key is "used by get_school", which hints at a chaining pattern (search first, then fetch details). It gives no explicit when-to-use / when-not guidance and does not say how it differs from find_schools or compare_schools, leaving the agent to infer selection.

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