Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

streeteasy_building

Fetch public building facts, amenities, policies, and sale or rental listings from a StreetEasy /building/{slug} page. Enter the building slug to get clean JSON details.

Instructions

Get StreetEasy building details. Retrieves public building facts, location, description, policies, amenities, and available sale/rental listing cards from StreetEasy's server-rendered building page. Pass the building slug from a StreetEasy /building/{slug} URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesStreetEasy building slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4/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. 'Public building facts' and 'Get/Retrieves' imply a safe read of public data and it names the data source (server-rendered building page), but it omits auth requirements, rate limits, or behavior on an invalid slug, leaving gaps for a mutation-free read tool.

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, purpose front-loaded, with the field enumeration earning its place because there is no output schema to convey return contents. Nothing is redundant.

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-parameter tool with 100% schema coverage and no output schema, the description covers what is returned (compensating for the missing output schema) and how to supply the slug. It could be complete with a note on failure behavior or freshness, but is adequate as-is.

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% (the slug property is described), so a baseline of 3 applies; the description adds value by explaining where the slug comes from (a /building/{slug} URL), which the schema does not. It stops short of stating slug format or edge-case handling.

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?

Specific verb+resource ('Get StreetEasy building details') followed by an enumerated scope: building facts, location, description, policies, amenities, and sale/rental listing cards. This building-level scope implicitly but clearly distinguishes it from siblings like streeteasy_unit, streeteasy_school, and streeteasy_areas.

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?

Tells the agent how to source the parameter ('Pass the building slug from a StreetEasy /building/{slug} URL'), which is useful invocation guidance, but gives no explicit when-to-use vs when-not, and never names alternatives such as streeteasy_unit or the search tools for agents that don't already have a slug.

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