Skip to main content
Glama

Attom

by io.github.pipeworx-io

Attom Rental Avm

attom_rental_avm
Read-onlyIdempotent

"How much can I rent [house] for" / "estimated rent for [address]" / "rental income on [property]" / "rental yield of [home]" — rental AVM for a US residential property. Returns estimated monthly rent, rental yield percentage, and rental value range. Use for landlord / investor / cash-flow analysis questions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
_apiKeyYesATTOM API key
address1YesStreet address (e.g., "123 Main St")
address2YesCity, state ZIP (e.g., "Denver, CO 80202")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, etc. The description adds that the tool returns rent, yield, and range, but does not disclose behavioral traits like error handling, rate limits, or address validation. It does not contradict annotations.

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?

The description is concise (about 50 words) and front-loaded with example questions. Every sentence adds value, though it could be more structured with bullet points. No wasted words.

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?

Given the tool's simplicity (3 required params, no enums) and presence of an output schema, the description adequately covers what the tool does and returns. It does not explain error scenarios or prerequisites, but the annotations and schema compensate.

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% with clear parameter descriptions. The description provides context but no additional semantics beyond the schema. Baseline 3 is appropriate.

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 clearly states the tool provides rental AVM for US properties, returning estimated monthly rent, rental yield, and range. It distinguishes itself from sibling tools like attom_avm (property value) by focusing on rental income, though it does not explicitly name siblings.

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 gives example queries and mentions use cases (landlord/investor/cash-flow analysis), but does not specify when not to use it or provide alternatives. The context is clear but lacks exclusionary guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Attom toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation2/5

Several tools overlap heavily: ask_pipeworx_beta is explicitly identical to ask_pipeworx right now, and ask_pipeworx_grounded shares the same router. The universal ask_pipeworx router also subsumes many domain-specific tools (attom_*, entity_profile, etc.), making it unclear when to use the specialist tools versus the catch-all.

Naming Consistency3/5

All names are snake_case and mostly descriptive, but conventions vary: ask_* and attom_* prefixes coexist with bare verbs (remember, forget, subscribe), noun phrases (entity_profile, polymarket_edges), and adjective-prefixed names (recent_alerts, recent_changes). The pattern is readable but not uniform.

Tool Count2/5

39 tools is well over the 25+ threshold for a heavy surface, especially for a server named 'Attom' that also includes memory, subscriptions, feedback, npm scanning, and AI-visibility tools beyond real estate. Many tools could be consolidated (e.g., the three ask_pipeworx variants, the six polymarket tools).

Completeness4/5

The real estate domain is well covered (search, detail, AVM, rental AVM, sales history, trends, assessment, schools), and the broader data platform includes discovery, grounded answers, entity profiles, comparisons, claim validation, subscriptions, and memory. Minor gaps exist only around edge features like OAuth-gated subscription persistence.

Resources