Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

streeteasy_school

Retrieve public school facts from StreetEasy by school slug, including neighborhood, grades, district, address, phone, and fax.

Instructions

Get StreetEasy school details. Retrieves the public school facts rendered on StreetEasy, including neighborhood, grade labels, district, address, phone, and fax when available. Use the school slug from a public /nyc/school/{slug} link, including the school results returned by streeteasy-quick-search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesStreetEasy school slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It implies a read-only public fetch ('public school facts rendered on StreetEasy') and discloses the returned fields, but says nothing about authentication, rate limits, error behavior for invalid slugs, or the missing-data cases beyond 'when available'.

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 tight sentences, front-loaded with the purpose, then the returned fields, then the slug-sourcing instruction. No filler or repetition.

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 single-param lookup with no output schema, the description covers purpose, return fields, and input provenance well. It could be rounded out with failure behavior for bad slugs, but nothing essential for correct invocation is missing.

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 coverage is 100% and the schema already describes 'slug' as the StreetEasy school slug, so the baseline is 3. The description adds real value by explaining the slug's provenance (the /nyc/school/{slug} URL form and the quick-search source), which is more than the schema 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?

States a specific verb+resource ('Get StreetEasy school details') and enumerates the exact facts returned (neighborhood, grade labels, district, address, phone, fax). It clearly distinguishes itself from siblings like streeteasy_building and streeteasy_unit by being the school-entity lookup.

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?

Explicitly tells the agent where the required slug comes from: a public /nyc/school/{slug} link or results from streeteasy-quick-search. This is actionable context, though it doesn't state when NOT to use this tool or what to do if no slug is available.

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

Deploy Server

Other Tools