Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

streeteasy_market_inventory

Read-only

Get StreetEasy's historical monthly sales and rental inventory for every area in its public Data Dashboard. Optionally bound the range with start_month and end_month in YYYY-MM format; defaults to the latest 12 months available and caps ranges at 36 months.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "streeteasy_market_inventory"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_monthNoLast month to return, inclusive, in YYYY-MM format. Defaults to the latest month available.
start_monthNoFirst month to return, inclusive, in YYYY-MM format. Defaults to the first month in the latest 12 months available.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real behavioral context beyond that: the default of the latest 12 months and the hard 36-month range cap, both of which affect invocation. It stops short of describing coverage limits (which areas, currency) or pagination.

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 tight sentences with the core purpose front-loaded and the range constraints second. No filler, though the parameter format detail slightly overlaps the schema.

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 an output schema present, return values need not be explained, and the annotations cover the safety profile. The description supplies the range defaults and cap, leaving it nearly complete for a read-only data-retrieval tool; only area scoping/coverage detail is absent.

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%, so both parameters are already documented in the schema, making 3 the baseline. The description mostly restates the YYYY-MM format and defaults, adding only the 36-month cap constraint as new information.

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?

The description names a specific verb (Get) and resource (historical monthly sales and rental inventory across every area in StreetEasy's Data Dashboard), so the agent knows exactly what data comes back. It does not, however, distinguish itself from close siblings like streeteasy_market_data_series or streeteasy_market_indices, leaving that differentiation to be inferred.

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?

It explains the optional date bounding and the default window, which implies when the parameters matter, but gives no explicit guidance on when to choose this tool over the related market-data siblings. Usage is inferable rather than stated.

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

All Crawlora MCP toolsInspect
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