Skip to main content
Glama

BRAINIAC Public Infrastructure Lookups

Ofsted school rating lookup

public-infrastructure_ofsted-rating-lookup
Read-onlyIdempotent

Look up the latest Ofsted inspection outcomes for a state-funded school in England. Price $0.02 USDC. POST /api/v1/public-infrastructure/ofsted-rating-lookup. An unpaid call returns the x402 payment terms and does not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "public-infrastructure_ofsted-rating-lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
urnNourn, string, length 1 to 20. Optional.
nameNoname, string, length 3 to 200. Optional.
limitNolimit, integer, from 1 to 25. Required.
laestabNolaestab, string, length 1 to 20. Optional.
postcodeNopostcode, string, length 2 to 12. Optional.
localAuthorityNolocalAuthority, string, length 2 to 100. Optional.

Output Schema

NameRequiredDescriptionDefault
asAtNoasAt. String.
schoolsNoschools. Array.
sourcesNosources. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the exact price ($0.02 USDC), the POST endpoint, and that an unpaid call returns x402 payment terms without executing — critical behavior an agent would otherwise discover only by failure. With readOnly/idempotent/non-destructive already declared, the remaining gaps (rate limits, result freshness) are minor.

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?

Three front-loaded sentences with zero waste: purpose first, then price and endpoint, then the payment-gate consequence. Every element an invoking agent needs is in the opening line.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and the payment model is covered. However, for a six-parameter search-style lookup with no required fields, the absence of any guidance on which identifier to supply leaves a real operational gap that the description should close.

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 the six parameters are already documented at the field level and a baseline of 3 applies. The description adds nothing about identifier precedence (urn vs laestab vs name vs postcode), whether filters combine, or why 'limit' is labeled required in its own description despite no required fields.

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 ('Look up the latest Ofsted inspection outcomes'), plus the scope ('state-funded school in England'), which distinguishes it cleanly from sibling public-infrastructure lookups such as college-scorecard or visa-waiver.

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: an agent can infer this is a read lookup for a single school's rating, but the description gives no explicit when-to-use/when-not guidance and no routing to alternatives for other education data. It also does not say how to choose among the several optional identifiers.

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