Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

streeteasy_market_indices

Read-only

Get StreetEasy's historical sale-price and rent index values 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 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_indices"
  }
}

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

A4/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 detail beyond that: the default window (latest 12 months) and the hard 36-month cap on ranges, which an agent could not infer from the annotations.

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 tight sentences: purpose first, then parameter/limit behavior. Every clause carries information and nothing is padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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-value documentation is not needed. The description covers scope, both optional parameters, defaults, and the range cap, leaving nothing an agent needs in order to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description goes beyond the schema by disclosing the 36-month cap and clarifying the default window behavior, adding meaning the schema does not contain. The YYYY-MM format reiterates the schema, so it is not a full 5.

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 states a specific verb ('Get') and resource ('StreetEasy's historical sale-price and rent index values') and scopes it to 'every area in its public Data Dashboard.' It is clearly distinguishable in intent, though it does not explicitly name which sibling (e.g. streeteasy_market_data_series) it supersedes, so it stops short of a 5.

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?

The description explains how to use the tool (optional start_month/end_month bounding, defaults, cap) but gives no explicit when-to-use vs. when-not-to-use guidance relative to the many streeteasy market/data siblings. Usage is implied by the resource described 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