Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

greystar_property

Fetch a Greystar apartment community profile by numeric property ID to view amenities, floor plans, fees, and available units with prices and dates. Get IDs from search.

Instructions

Get a Greystar apartment community. Retrieves a public Greystar community profile by its numeric property id: location, description, amenities, office hours, walk scores, tours, floor plans, published fees, and currently available units with starting prices and available dates. Get ids from /greystar/search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesNumeric Greystar property id, e.g. 10124

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does reasonably well: 'public' signals no auth is required and the read-only verb confirms it's a fetch. It details what the payload contains (hours, fees, available units with prices/dates), which helps the agent anticipate results, though it mentions no rate limits or error behavior.

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 dense sentences: the first names the tool's function, the second enumerates returned fields, and the id-source hint is tucked at the end. No filler and well front-loaded.

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?

There is no output schema, so the description must describe return values, and it does so thoroughly (location, amenities, walk scores, floor plans, fees, available units with prices and dates). Combined with the id-source guidance, an agent has everything needed 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% and already documents the numeric id with an example, so the baseline is 3. The description adds real value by telling the agent where to obtain a valid id (/greystar/search), which the schema does not.

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 and resource ('Get/Retrieves a public Greystar community profile by its numeric property id') and enumerates exactly what data is returned. This lets an agent distinguish it immediately from siblings like greystar_search or greystar_units.

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?

Points the agent to the id source ('Get ids from /greystar/search'), which effectively names the prerequisite and the alternative tool for discovery. It doesn't explicitly state when NOT to use this tool (e.g. for bulk or non-id lookups), so it stops short of a full 5.

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