get_comps
Get recently sold comparable properties.
Args:
query: Address or area substring to match.
limit: Max results (1-100).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| query | No |
DealScanner
TDQS
A3.6/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It only explains parameters, not behavioral traits such as read-only nature, pagination, ordering, or other operational details.
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?
The description is minimal and to the point, with a clear purpose sentence and an organized Arg list. Every word earns its place without unnecessary fluff.
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 simple two-parameter query tool, the description covers the essential purpose and parameter semantics. It omits return format and edge cases, but given the low complexity, it is reasonably complete.
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?
The description adds meaningful semantics to both parameters: 'query' is clarified as an address/area substring, and 'limit' is given a range (1-100). The schema itself lacks descriptions, so this is valuable.
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?
The description uses a specific verb ('Get') and a clear resource ('recently sold comparable properties'), making it distinctly different from siblings like get_property or search_deals. It unambiguously states what the tool does.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives. There are no explicit conditions, exclusions, or references to sibling tools in the description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.9/5.0
Disambiguation3/5
Most tools are clearly distinct, but analyze_brrrr overlaps with get_property when given an address and strategy=brrrr, since both can return a BRRRR analysis. The ad-hoc input option for analyze_brrrr and the broader strategy support in get_property help clarify, yet the boundary is not fully crisp.
Naming Consistency4/5
Tool names are mostly snake_case with a verb_object pattern (analyze_brrrr, get_comps, get_property, search_deals), but area_stats and top_investment_areas are noun phrases, and whoami is a standalone command. These minor deviations are easy to predict and remember.
Tool Count5/5
With 7 tools, the server is well-scoped for a real estate deal analysis domain. Each tool covers a distinct high-level task (search, analysis, comps, stats, ranking, identity) without unnecessary redundancy or excessive fragmentation.
Completeness4/5
The surface covers the core lifecycle: searching deals, analyzing properties (flip, rental, brrrr), pulling comps, getting area stats, and ranking areas. A minor gap is the lack of a dedicated 'analyze_flip' or 'analyze_rental' tool, but get_property with strategy handles those cases, so no dead ends.