Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

streeteasy_market_inventory

Retrieve monthly StreetEasy sales and rental inventory counts for every area, with optional start and end months up to a 36-month range.

Instructions

Get StreetEasy monthly market inventory. Returns monthly sales and rental inventory counts for every area in StreetEasy's public Data Dashboard. Defaults to the latest 12 available months; each request is limited to 36 months.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
end_monthNoLast month, inclusive, in YYYY-MM format; defaults to the latest available month
start_monthNoFirst month, inclusive, in YYYY-MM format

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

B3.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 behavioral burden, and it does disclose two useful traits: the 12-month default window and the 36-month per-request ceiling. However, it says nothing about permissions, whether data is cached/static, rate limits, or how areas are keyed in the response, leaving the operation's practical constraints partly opaque.

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?

Three sentences, each carrying a distinct payload (what it returns, default window, hard limit), with the purpose front-loaded. Slightly tighter phrasing could merge the last two clauses, but there is no filler.

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 two-parameter, no-annotation, read-only retrieval tool with no output schema, the description covers purpose, scope (all areas), response contents, and range limits. It is nearly sufficient; only the absence of any linkage to sibling market tools keeps it from being fully complete.

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% and both parameters (start_month, end_month) are fully documented in YYYY-MM format, so the baseline is 3. The description adds marginal value by clarifying the default span (12 months) and the hard cap (36 months), which the schema does not express, but it does not resolve defaults for start_month specifically.

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?

Uses a specific verb and resource ('Get StreetEasy monthly market inventory') and states what the response contains (monthly sales and rental inventory counts for every area in StreetEasy's public Data Dashboard). It is clear on its own, but it never distinguishes itself from closely named siblings such as streeteasy_market_data_series or streeteasy_market_indices, so an agent must infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description never states when to choose this tool over streeteasy_market_data_series, streeteasy_market_indices, or streeteasy_market_data_catalog. It only mentions operational defaults (latest 12 months, 36-month cap), which is behavior, not selection guidance.

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