Crawlora MCP

streeteasy_school

Read-only

Get public StreetEasy school-profile facts by the slug used in its /nyc/school/{slug} URL. School slugs from streeteasy_quick_search can be used here.

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": {
      "slug": "<slug>"
    },
    "name": "streeteasy_school"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	StreetEasy school slug from a public /nyc/school/{slug} URL or streeteasy_quick_search result.

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.

First observedOct 7, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, covering the safety profile. The description adds that data is 'public' (implying no auth) and that slugs derive from a public URL, but does not describe rate limits, response shape, or other behavioral traits. With annotations doing the heavy lifting, this is adequate but not rich.

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 sentences, front-loaded with the purpose and identifier pattern. The second sentence about slug source is brief but partly duplicates the schema description; still, there is no wasted verbiage.

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

Completeness5/5

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

For a one-parameter detail lookup with a full output schema, the description covers what data is returned and how to obtain the required slug. Nothing an agent needs to call it correctly is missing, and return values are delegated to the output schema.

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 coverage is 100% and the single slug parameter is fully documented in the schema, including its source from the URL or quick_search. The description mirrors that schema text rather than adding syntax or format details, 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?

States a specific verb 'Get' and resource 'public StreetEasy school-profile facts', and pins the identifier to the /nyc/school/{slug} URL pattern. This distinguishes it from search-oriented siblings like streeteasy_quick_search and from other StreetEasy detail tools by naming the exact profile type.

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?

Provides only a pointer to streeteasy_quick_search as a slug source; it does not state when this lookup is preferable to other siblings or any exclusions. Usage is implied (when you already have a school slug) but not explicitly framed.

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.