Crawlora MCP

streeteasy_building

Read-only

Get a StreetEasy building by its URL slug, including building type, location, year/floor/unit facts, description, policies, amenities, available sale/rental counts, and listing cards. Use the segment after /building/ in a public StreetEasy building URL; use streeteasy_areas for search area IDs.

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_building"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	StreetEasy building slug from a public /building/{slug} URL.

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.9/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, covering the safety and network profile. The description's field enumeration overlaps the output schema rather than adding behavioral context like caching, access restrictions, or failure modes, so it clears the lowered bar but only modestly.

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 primary action and followed by the input-sourcing and alternative guidance. The long field enumeration is somewhat listy and partly redundant with the output schema, but the text is still efficient.

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 one required parameter, full schema coverage, an output schema, and annotations all present, the description covers what remains: the resource identity and how to form the slug. Nothing critical for correct invocation is missing.

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% and the single slug parameter is already documented there. The description adds the URL-derivation hint, which reinforces but does not substantially extend what the schema provides, so the 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 (StreetEasy building) and enumerates the returned entity's composition. It also distinguishes itself from streeteasy_areas, so an agent can tell the two apart without inspecting schemas.

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?

Specifies exactly how to obtain the slug ('the segment after /building/ in a public StreetEasy building URL') and routes area-ID needs to streeteasy_areas. It lacks an explicit when-not-to-use clause, but the input derivation and sibling routing are clear.

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.