Crawlora MCP

streeteasy_unit

Read-only

Get a public StreetEasy unit listing from its building slug and unit segment, including asking price, description, address, amenities, and open-house events. Use the path segments from a public /building/{slug}/{unit} URL.

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": {
      "building_slug": "<building_slug>",
      "unit": "<unit>"
    },
    "name": "streeteasy_unit"
  }
}

Input Schema

Name	Required	Description	Default
`unit`	Yes	Unit path segment from a public /building/{slug}/{unit} URL.
`building_slug`	Yes	StreetEasy building slug from a public /building/{slug}/{unit} 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 5, 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 and openWorldHint. The description adds that the listing is public (implying no auth) and lists some fields, but does not elaborate on rate limits, pagination, or error behavior beyond what the output schema already covers.

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 sentences, front-loaded with the action and then the input sourcing. Every word earns its place with no redundancy.

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 simple two-parameter read-only retrieval tool with full schema coverage, existing annotations, and an output schema, the description provides adequate purpose and input guidance. 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.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% with clear per-parameter descriptions already explaining they are path segments from a /building/{slug}/{unit} URL. The description mirrors this information without adding new semantic detail, so the baseline score of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 unit listing') and enumerates the returned fields, making the scope clear. It does not explicitly differentiate from siblings like streeteasy_building or streeteasy_rentals_search, but an agent can infer this is a single-listing 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?

The second sentence clearly tells the agent where to source the required parameters: 'Use the path segments from a public /building/{slug}/{unit} URL.' It gives no exclusions or named alternatives, but the input context is explicit.

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.

Resources

Need Help?