Skip to main content
Glama

Attom

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Attom Property Detail

attom_property_detail
Read-onlyIdempotent

"Property details for [address]" / "specs of [house]" / "how many bedrooms / bathrooms" / "year built" / "square footage" / "lot size" — full property characteristics for a US residential or commercial address. Returns lot size, square footage, bedrooms, bathrooms, year built, construction type, and heating/cooling systems from ATTOM Data Solutions (the premium US real estate dataset). Use whenever an agent needs structured property attributes by address.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "Property detail response from ATTOM API",
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-attom-api-key",
+    "address1": "123 Main St",
+    "address2": "Denver, CO 80202"
+  },
+  {
+    "_apiKey": "your-attom-api-key",
+    "address1": "456 Oak Avenue",
+    "address2": "Austin, TX 78701"
+  }
+]
  3. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false, so the description complements them by listing example attributes (bedrooms, bathrooms, etc.) and noting the data source (ATTM Data Solutions). No contradictions; adds some behavioral context beyond 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 two sentences plus example queries, front-loaded with the core purpose and examples. Every sentence adds value with no redundancy or fluff.

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?

The description explains the tool's output (property characteristics), data source, and usage context ('for a US residential or commercial address'). With an output schema present, no additional return value details are needed. Complete for its complexity.

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%, so the schema already explains all parameters. The description does not add new semantics beyond the schema's field descriptions and examples. Baseline 3 is appropriate.

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 specific verbs and resources ('returns full property characteristics') and distinguishes from sibling tools like attom_assessment and attom_property_search by focusing on structured attribute lookup by address. Example queries like 'how many bedrooms / bathrooms' reinforce the purpose.

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?

The description explicitly says 'Use whenever an agent needs structured property attributes by address,' providing clear context. It does not explicitly state when not to use it or mention alternatives, but the sibling tools list and the tool's specificity imply appropriate use cases.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources