Skip to main content
Glama

find_nurseries

Read-onlyIdempotent

Find nurseries, pre-schools and out-of-school clubs registered with Ofsted near a postcode or place in England, with places and the latest Ofsted grade. Childminders are not included.

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

Input Schema

NameRequiredDescriptionDefault
typeNoall, full_day (nurseries open all day), sessional (pre-schools) or out_of_school (default all)
limitNoMost providers to return, nearest first, 1 to 100 (default 25)
locationYesA UK postcode or a town, city or district in England
radius_kmNoSearch radius in kilometres, 0.5 to 15 (default 2)

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds real context beyond them: results carry places and the latest Ofsted grade, coverage is England-only, and childminders are excluded from results. Return shape and nearest-first ordering are left to the schema, which is a minor gap.

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?

Two sentences with no waste: the capability and its domain are front-loaded, and the exclusion clause is placed last where it reads as a qualifier. Nothing redundant or padded.

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 four-parameter read-only search with full schema coverage, the definition covers purpose, domain, result fields and one exclusion. Only a brief nod to result ordering (nearest-first) or the England-only limitation on the location parameter would make it airtight.

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%, with each of the four parameters documented in the schema, so the baseline is 3. The description only echoes the location concept ('near a postcode or place in England') and adds no syntax or format detail beyond what the schema already states.

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 names a specific verb and resource ('Find nurseries, pre-schools and out-of-school clubs') and pins down the domain ('registered with Ofsted', 'in England'). It also states an explicit scope exclusion ('Childminders are not included'), which cleanly separates it from the broader sibling find_schools.

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?

The scope statement implies when to reach for this tool (location-based search for early-years providers), and the childminder exclusion clarifies one boundary. However, it never routes the agent explicitly to siblings such as find_schools for schools or search_schools_by_name for name lookups, so the when-to-use-vs-alternatives guidance is only implied.

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