Crawlora MCP

tes_school_search

Read-only

Search the Tes Schools Directory by name or location; returned school IDs can be used with tes_job_employer. Use tes_job_search to find openings.

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": {
      "query": "<query>"
    },
    "name": "tes_school_search"
  }
}

Input Schema

Name	Required	Description
`page`	No	One-based page
`query`	Yes	School name or location
`page_size`	No	Results per page

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 7, 2026
- addedInput schema / properties / page / description
```
Added value: +"One-based page"
```
- addedInput schema / properties / page_size / description
```
Added value: +"Results per page"
```
- addedInput schema / properties / query / description
```
Added value: +"School name or location"
```
First observedOct 7, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is known. The description adds the chaining context (IDs usable downstream) but says nothing about pagination behavior, result caps, or ranking, which matters for a paged search endpoint.

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 tight clauses separated by a semicolon: what it searches and what to do with the result, plus one routing hint. Every clause earns its place and there is no filler.

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 3 params at full schema coverage, annotations covering safety, and an output schema present, the description covers purpose, output usage, and sibling routing. It lacks pagination guidance, but that is minor given the structured fields already present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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, but the description adds real value by telling the agent the school IDs returned can be fed to tes_job_employer. It clarifies the output's purpose beyond the parameter definitions.

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 (Search) and resource (Tes Schools Directory) with the searchable fields (name or location). It also names the sibling tes_job_employer and the downstream use of the returned school IDs, clearly distinguishing it from job and resource search siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear positive guidance that returned IDs feed into tes_job_employer and points to tes_job_search for openings. It does not state when NOT to use it (e.g., for browsing all schools without a query), so it stops short of full when/when-not coverage.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.