Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

streeteasy_market_indices

Retrieve StreetEasy monthly sale-price and rent index values by dashboard area for a chosen date range, defaulting to the latest 12 months and capped at 36.

Instructions

Get StreetEasy monthly market indices. Returns public sale-price and rent index values by dashboard area. The datasets have different historical start dates; missing values are omitted. Defaults to the latest 12 months and limits each request 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

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that datasets have different historical start dates, that missing values are omitted, that the default window is the latest 12 months, and that requests are capped at 36 months. Auth requirements and exact return shape are not covered, but the operational constraints are unusually well surfaced for an unannotated 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences with no waste, front-loaded with purpose and return content, then constraints. Each sentence carries distinct information (what it returns, data caveats, range limits).

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-optional-parameter read tool with no annotations and no output schema, the description covers purpose, return content, defaults, and hard limits. The only real gap is the absence of any pointer to the sibling market-data tools, which would complete the routing picture.

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 already document the YYYY-MM format and the end_month default, so the baseline is 3. The description adds the 36-month request cap, which is a constraint not expressible in the schema, but otherwise adds little beyond what the parameter descriptions provide.

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 ('StreetEasy monthly market indices') and specifies the return content (public sale-price and rent index values by dashboard area). It does not explicitly name the closely related siblings (streeteasy_market_data_series, streeteasy_market_data_catalog), so the agent must infer the distinction from the sibling names alone.

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?

Usage is implied through the default window ('latest 12 months') and the 36-month cap, which tells the agent this is a bulk historical index fetch. There is no explicit statement of when to prefer this over streeteasy_market_data_series or the catalog tool, so the routing decision is left to inference.

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