Find Indian-American realtors & real-estate agencies.
Provide a point (`lat`+`lng`, optional `radius_miles`) or `city`/`state`. Filter by `tag`
(e.g. "agency", "mortgage").
| Name | Required | Description | Default |
|---|---|---|---|
| lat | No | ||
| lng | No | ||
| tag | No | ||
| city | No | ||
| limit | No | ||
| state | No | ||
| offset | No | ||
| open_now | No | ||
| radius_miles | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Input schema / properties / offsetAdded value: +{
+ "default": 0,
+ "title": "Offset",
+ "type": "integer"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description must fully disclose behavioral traits. It describes two search modes and a filter, but omits crucial details: pagination behavior (limit, offset), the meaning of 'open_now' for real estate, handling of conflicting parameters (both location and city/state), and whether results are sorted or ranked. Incomplete disclosure for a tool with 9 parameters.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with purpose. Could list the modes more explicitly (e.g., bullet points), but overall concise and readable. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given 9 parameters, 0% schema description coverage, and an output schema (contents unknown), the description is insufficient. It does not explain pagination, return format, default radius, or behavior with missing required parameter combinations. For a complex search tool, more detail is needed to ensure correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema has 0% description coverage for parameters. Description clarifies lat, lng, radius_miles, city, state, and tag, but omits limit, offset, and open_now. open_now is particularly confusing for real estate and requires explanation. The description partially compensates for the missing schema descriptions but does not cover all parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the verb 'Find' and resource 'Indian-American realtors & real-estate agencies', and distinguishes two search modes (location-based or city/state) plus optional tag filter. This differentiates it from sibling tools like search_realestate_by_text (text search) and get_realestate_details (details on a specific entity).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Description provides explicit usage instructions: 'Provide a point (lat+lng, optional radius_miles) or city/state. Filter by tag.' However, it does not state when to use this tool over alternatives, nor does it mention when not to use it (e.g., unsupported locations). No explicit guidance on parameter combinations or conflicts.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.