Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

greystar_unit_locations

List all valid Greystar unit search locations (nationwide, states, metros, cities, neighborhoods) and drop those without listings.

Instructions

List Greystar unit search locations. Lists every location accepted by /greystar/units: the nationwide us listing, states, metros, cities, and neighborhoods (nested ones carry their parent), taken from the site's own search pages. Locations Greystar has no unit listing for are dropped once detected.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoText matched against the location slug, e.g. austin

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 behavioral burden and does disclose useful traits: nested locations carry their parent, and locations Greystar has no unit listing for are dropped once detected. These are non-obvious dynamics beyond the schema. It does not describe return format or pagination, but that is a minor gap for a read-only list.

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?

Front-loads the purpose in the first sentence, then supports it with scope and behavior in two more. Slightly redundant in restating 'Lists every location accepted by /greystar/units' but overall efficient and well-ordered.

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 single optional-param list tool with no annotations or output schema, the description covers purpose, scope, hierarchy, and filtering behavior adequately. Only the absence of any return-structure hint 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 description coverage is 100%, so the single query parameter is fully documented in the schema (text matched against the location slug, e.g. austin). The description adds no syntax or matching detail beyond that, so the baseline 3 applies.

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 (List) and resource (Greystar unit search locations), and enumerates the content hierarchy: nationwide US listing, states, metros, cities, neighborhoods. It ties the tool to /greystar/units, but does not explicitly distinguish itself from similarly named siblings like greystar_locations or greystar_markets.

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 phrase 'locations accepted by /greystar/units' implies the use case (discovering valid location values for the units search), but there is no explicit when-to-use, when-not-to-use, or reference to the greystar_locations/greystar_markets alternatives. Usage must be inferred.

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