Skip to main content
Glama
Sign In

DealMachine

by io.github.DealMachine
OverviewDiscussionsAdmin

dealmachine_enrich_apn

Destructive

Finds who owns a property from its Assessor's Parcel Number: one apn, or up to 250 in data sharing the same location and options. A location narrows the match, and APN formatting is normalized automatically. Returns the property details; with contact_audience=owners it also returns the owners with their names, phones (with DNC flags) and emails. Contacts are left out unless contact_audience is set. Needs a connected DealMachine account with paid access. Each matched property costs one property credit and returned contacts cost people credits.

Input Schema

NameRequiredDescriptionDefault
apnNoAssessor's Parcel Number (e.g. "0123-45-6789")
dataNoBatch of parcel lookups sharing the location and requested fields. Prefer one batch when the user requests multiple lookups.
fieldsNoDealMachine property field IDs to include in results
locationNoOptional location to narrow results, including a city place ID
contact_audienceNo`none` returns property-only data with zero people credits; other values include matching contacts

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / data
      Added value: +{
+  "description": "Batch of parcel lookups sharing the location and requested fields. Prefer one batch when the user requests multiple lookups.",
+  "items": {
+    "properties": {
+      "apn": {
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "apn"
+    ],
+    "type": "object"
+  },
+  "maxItems": 250,
+  "minItems": 1,
+  "type": "array"
+}
    • removedInput schema / required
      Removed value: -[
-  "apn"
-]
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already mark the tool as non-read-only/destructive, and the description goes further by disclosing paid-account requirements and per-property/per-contact credit costs, plus that returned phones carry DNC flags. It doesn't discuss rate limits or error behavior, so not a 5.

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?

One dense paragraph front-loads purpose and batch limits, then layers cost and return details. Every sentence adds information, though the block could be split for faster scanning.

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?

Covers return contents, account prerequisites, credit costs, and contact behavior, which is substantial for a 5-param tool without an output schema. It leaves out error/empty-result handling and how the fields array influences returned details.

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?

Schema coverage is 100%, so baseline is 3; the description adds value by explaining that APN formatting is normalized automatically, that data batches share location/options, and how contact_audience governs contact inclusion.

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?

States a specific verb ('Finds who owns') and resource ('Assessor's Parcel Number'), plus batch scope (one apn or up to 250 in data). This clearly differentiates it from siblings like enrich_address or enrich_latlng, which take other identifiers.

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?

Provides operational context—batch limit, location narrowing, and that contacts are omitted unless contact_audience is set—but never says when to choose this tool over enrich_address or enrich_latlng. Usage is implied by the APN input rather than explicitly guided.

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

All DealMachine 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