Skip to main content
Glama

get_school

Read-onlyIdempotent

Full profile of one school by URN: details, admissions policy, Ofsted inspection outcomes, and every published measure (results, attendance, admissions demand, pupils, finance, staffing, Parent View) with its latest year, England and local authority medians, how it compares with similar schools, and recent trend.

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

Input Schema

NameRequiredDescriptionDefault
urnYesThe school key from search_schools_by_name: a six-digit URN, or seven digits for a Welsh school not in GIAS or a Northern Ireland school
include_subjectsNoAlso return GCSE results for each subject (adds many rows)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (read-only, idempotent, closed-world), so the description's added value is in disclosing what the response contains, which it does in detail, including per-measure latest year, national and local authority medians, similar-school comparisons, and trends. With no output schema, that return-shape disclosure is the key contribution; it stops short only of mentioning response size or the cost of the broad profile.

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?

A single front-loaded sentence opens with the verb and resource before the long enumeration of covered measures, so nothing important is buried. The measure list is dense but each item earns its place by telling the agent what data comes back.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 returns and does so thoroughly, naming each measure family and the comparison dimensions (medians, similar schools, trend). Combined with 100% schema coverage on the two parameters, an agent has everything needed to call this correctly.

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 both urn and include_subjects are already documented, and the description adds only the 'by URN' framing. It says nothing extra about include_subjects' effect beyond what the schema's 'adds many rows' already states, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Full profile of one school by URN') and then enumerates exactly what that profile contains: details, admissions policy, Ofsted outcomes, and every published measure. The singular 'one school' scope makes it easy to distinguish from compare_schools or find_schools at a glance.

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: the URN-based lookup and the schema note that the key comes from search_schools_by_name sketch a workflow, but the description never says when to prefer this over compare_schools or rank_schools, nor any exclusion. An agent can infer the single-school use case but gets no explicit routing guidance.

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