Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

streeteasy_market_data_series

Read-only

Get one StreetEasy public dashboard metric for every published area. Use dataset IDs from streeteasy_market_data_catalog; optional start_month and end_month are YYYY-MM and ranges are capped at 36 months.

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": {
      "dataset": "<dataset>"
    },
    "name": "streeteasy_market_data_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
datasetYesStreetEasy dashboard dataset ID from streeteasy_market_data_catalog.
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

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds a genuine behavioral constraint not in the annotations: month ranges are capped at 36 months, which affects how an agent must chunk requests.

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 core action and followed by the essential sourcing constraint and range cap. Zero 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?

An output schema exists, so return values need not be described. The description covers the dataset source, temporal inputs, and range limit. Minor gap: it doesn't state whether all published areas are always returned or whether filters exist beyond the month range.

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 all three parameters are fully documented in the schema, including YYYY-MM formats and defaults. The description restates the YYYY-MM format and adds the 36-month cap, but adds little parameter meaning beyond the schema baseline.

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

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Get'), a precise resource ('one StreetEasy public dashboard metric for every published area'), and names the sibling catalog tool that supplies valid dataset IDs. An agent can distinguish this from streeteasy_market_indices or streeteasy_market_inventory without opening any schema.

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?

Explicitly routes the agent to streeteasy_market_data_catalog for dataset IDs, which is the key prerequisite. It does not, however, state when to prefer this series tool over the other streeteasy market tools, so no explicit when-not guidance.

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