Skip to main content
Glama

Altos

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Altos Active Listings

altos_active_listings
Read-onlyIdempotent

Search active property listings in a region (e.g., "Denver, CO"). Returns address, price, beds, baths, square footage, and listing status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoDate (must be a Friday, YYYY-MM-DD). Defaults to most recent Friday.
limitNoMax rows to return (default 100)
regionYesRegion code (e.g., "ca_los-angeles", "ca_94105")
_altosKeyYesAltos Research API key

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesFriday date (YYYY-MM-DD) for snapshot
regionYesRegion code queried
listingsYesActive property listings
returnedYesNumber of listings returned
total_availableYesTotal active listings in region

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "date": {
+      "description": "Friday date (YYYY-MM-DD) for snapshot",
+      "type": "string"
+    },
+    "listings": {
+      "description": "Active property listings",
+      "items": {
+        "properties": {
+          "baths": {
+            "description": "Number of bathrooms",
+            "type": "string"
+          },
+          "beds": {
+            "description": "Number of bedrooms",
+            "type": "string"
+          },
+          "built_in": {
+            "description": "Year built",
+            "type": "string"
+          },
+          "city": {
+            "description": "City name",
+            "type": "string"
+          },
+          "days_on_market": {
+            "description": "Days on market",
+            "type": "string"
+          },
+          "floor_size": {
+            "description": "Floor area in square feet",
+            "type": "string"
+          },
+          "lot_size": {
+            "description": "Lot size in square feet",
+            "type": "string"
+          },
+          "price": {
+            "description": "Listing price",
+            "type": "string"
+          },
+          "property_id": {
+            "description": "Unique property identifier",
+            "type": "string"
+          },
+          "state": {
+            "description": "State abbreviation",
+            "type": "string"
+          },
+          "street_address": {
+            "description": "Property street address",
+            "type": "string"
+          },
+          "type": {
+            "description": "Property type",
+            "type": "string"
+          },
+          "zip": {
+            "description": "Zip code",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "region": {
+      "description": "Region code queried",
+      "type": "string"
+    },
+    "returned": {
+      "description": "Number of listings returned",
+      "type": "number"
+    },
+    "total_available": {
+      "description": "Total active listings in region",
+      "type": "number"
+    }
+  },
+  "required": [
+    "region",
+    "date",
+    "total_available",
+    "returned",
+    "listings"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_altosKey": "your-altos-api-key",
+    "region": "ca_los-angeles"
+  },
+  {
+    "_altosKey": "your-altos-api-key",
+    "date": "2024-01-12",
+    "limit": 50,
+    "region": "ca_94105"
+  }
+]
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds value by specifying the exact data fields returned (address, price, beds, baths, sq ft, status), which goes beyond the annotations. No contradiction detected.

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?

Single sentence that is front-loaded with the action 'Search active property listings'. Every word is necessary; no extraneous text. Efficient and clear.

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 covers the core behavior and returned fields. With an output schema present, detailed return value explanation is unnecessary. Minor omission: no mention of pagination or the format of region codes, but given the complexity, this is acceptable.

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?

The input schema has 100% description coverage—every parameter already has a description. The tool description does not add additional semantic meaning to the parameters, so it meets the baseline for high coverage without further elaboration.

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 clearly specifies searching active property listings with verb 'Search', identifies the resource ('active property listings'), and lists returned fields (address, price, beds, baths, sq ft, status). It distinguishes from sibling tools like 'altos_new_listings' and 'altos_pending_sales' by focusing on active listings.

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 is adequate for understanding what the tool does but offers no explicit guidance on when to use it versus alternatives like 'altos_new_listings' or 'altos_pending_sales'. It does not mention when not to use it or provide context for selecting this tool over others.

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

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