szkoly-mcp

Find schools and kindergartens (Poland)

find_schools

Read-only

Search Polish schools and kindergartens by town, gmina, address, or coordinates; filter by level and public status, and compare exam results with national averages.

Instructions

Schools or kindergartens in a Polish town / gmina or near an address: type, public or non-public, address, number of pupils, RSPO id, website and the latest exam results (eighth-grade exam for primary schools, matura pass rate and averages for licea/technika) vs the national average. place: town "Kórnik", gmina, address "Kraków, Długa 5" (sorted by distance) or 'lat,lon'.

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

Input Schema

Name	Required	Description
`max`	No	How many to list (default 12)
`sort`	No	Default: distance for addresses, results for school levels with exams
`level`	No	przedszkole, podstawowa, liceum, technikum, branzowa, policealna, artystyczna or dowolna (default)
`place`	Yes	Town, gmina, address or 'lat,lon' in Poland
`radius_km`	No	Only within this distance from the address
`public_only`	No	Only public schools

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 23, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description usefully adds that results include exam results benchmarked against the national average and that address queries sort by distance, but it says nothing about result caps beyond the schema, rate limits, or coverage caveats.

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 dense sentences: the first front-loads what the tool returns, the second documents the place input. No filler sentences, though the field enumeration makes the first sentence long and slightly run-on.

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 by enumerating the returned fields and the exam-result benchmarks, which is what an agent needs. It is nearly complete for a search tool, lacking only explicit guidance on sibling selection.

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 baseline is 3. The description reinforces the 'place' formats (town, gmina, address, 'lat,lon') and the distance-sorting implication, but this largely duplicates the schema rather than adding new semantics.

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 (find) and resource (schools and kindergartens in Poland), and enumerates the returned fields (type, address, pupil count, RSPO id, exam results). It is clearly distinguishable from school_details by its search/aggregation framing, though it never names that sibling explicitly.

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 by the 'place' input patterns and the mention of sorting by distance. There is no explicit statement of when to call this versus school_details or data_sources, nor any prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server