Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

streeteasy_market_data_series

Fetch monthly StreetEasy real estate market metrics for any published area. Specify a dataset and optional start/end months; defaults to the latest 12 months.

Instructions

Get one StreetEasy monthly market metric. Returns a public dashboard metric for every published area. Obtain the complete dataset ID set and its labels/dimensions from streeteasy-market-data-catalog. Defaults to the latest 12 months and limits requests to 36 months.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
datasetYesStreetEasy dashboard dataset ID
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.8/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 burden. It usefully discloses the default date range and the 36-month request ceiling, but says nothing about authentication, rate limits, response shape, or error behavior for invalid dataset IDs.

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?

Three tightly written sentences, front-loaded with the core action, then the catalog pointer, then the range constraints. No filler or repetition.

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 3-parameter tool with a fully documented enum schema, no output schema, and no annotations, the description covers purpose, dataset sourcing, date defaults, and the request cap. It is nearly complete, lacking only return-shape and threshold/error detail.

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%, so dataset, start_month, and end_month are already documented with formats and defaults. The description adds only the pointer to the catalog for valid dataset IDs, which is genuinely useful but not beyond baseline, so a 3 is appropriate.

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 and resource: 'Get one StreetEasy monthly market metric' returning a dashboard metric per published area. It is clear what the tool retrieves, though it does not explicitly distinguish itself from nearby siblings like streeteasy_market_indices or streeteasy_market_inventory.

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?

Gives a clear prerequisite/workflow: obtain the dataset ID set and labels/dimensions from streeteasy-market-data-catalog before calling. It also documents the default window (latest 12 months) and the hard limit (36 months). No explicit when-not or direct sibling comparison, but context is clear.

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