Skip to main content
Glama

Attom

by io.github.pipeworx-io

Attom Avm

attom_avm
Read-onlyIdempotent

"What's [house] worth" / "home value of [address]" / "Zestimate alternative" / "estimated value of [property]" / "how much is [home] valued at" — automated valuation model (AVM) for any US residential property. Returns ATTOM's estimated market value, confidence score, and low/high range. Use for instant home-price questions; pair with attom_sales_history for recent comparable sales.

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.8/5.0
Behavior4/5

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

Annotations already declare read-only and idempotent behavior. The description adds context by specifying return values (estimated market value, confidence score, low/high range) and scope (US residential properties), which go beyond the structured annotations.

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 three sentences, front-loaded with example queries, and each sentence serves a distinct purpose (examples, explanation, usage guidance). 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?

The description adequately covers the tool's purpose, output, and usage. An output schema exists to document return values. It could mention the API key requirement explicitly, but that is already in the schema.

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 coverage is 100% with clear parameter descriptions for address1, address2, and _apiKey. The description does not add further parameter-level meaning, so a baseline score of 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 it provides an automated valuation model for US residential properties and lists example queries. However, it does not explicitly differentiate from sibling ATTOM tools like attom_assessment or attom_rental_avm, which could cause confusion for an agent.

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?

It advises using for 'instant home-price questions' and suggests pairing with attom_sales_history, but does not specify when not to use it or contrast with alternatives like attom_assessment. Some context is provided, but exclusions are missing.

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