Skip to main content
Glama

compare_schools

Read-onlyIdempotent

Compare two to six schools by URN on key measures: Ofsted, results, admissions demand, attendance, pupil-teacher ratio, spending and pupil characteristics.

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

Input Schema

NameRequiredDescriptionDefault
urnsYesTwo to six school URNs

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 declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely useful behavioral context by enumerating what is actually compared (Ofsted, results, admissions demand, attendance, ratio, spending, pupil characteristics), which matters because 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence that states the operation, the input scope, and the compared measures with zero filler; every clause earns its place.

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 compensates well by naming the measures returned, and the input precondition is stated. It stops short of describing result structure (e.g., per-school blocks vs. side-by-side), a minor residual gap for a comparison tool.

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?

There is a single parameter with 100% schema description coverage ('Two to six school URNs'), and the description only restates the same cardinality constraint. Schema carries the semantics, 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?

The description gives a specific verb (Compare), a specific resource (schools by URN), an explicit cardinality range (two to six), and enumerates the comparison dimensions. This clearly distinguishes it from single-school retrieval (get_school) and ranking tools.

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 constraint 'by URN' and 'two to six schools', which tells the agent the input precondition, but there is no explicit statement of when to prefer this over siblings like get_school or rank_schools, nor any when-not 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