Skip to main content
Glama

Altos

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Altos New Listings

altos_new_listings
Read-onlyIdempotent

Get freshly listed properties (under one week on market) for a region (e.g., "Boston, MA"). Returns address, price, beds, baths, and listing date.

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
returnedYesNumber of new listings returned
new_listingsYesFreshly listed properties (under one week)
total_availableYesTotal new 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"
+    },
+    "new_listings": {
+      "description": "Freshly listed properties (under one week)",
+      "items": {
+        "description": "Raw CSV row data as key-value pairs",
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "region": {
+      "description": "Region code queried",
+      "type": "string"
+    },
+    "returned": {
+      "description": "Number of new listings returned",
+      "type": "number"
+    },
+    "total_available": {
+      "description": "Total new listings in region",
+      "type": "number"
+    }
+  },
+  "required": [
+    "region",
+    "date",
+    "total_available",
+    "returned",
+    "new_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": 100,
+    "region": "us_national"
+  }
+]
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and no destructive behavior. The description adds value by listing return fields (address, price, beds, baths, listing date), enhancing transparency beyond annotations. No contradictions.

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 a single sentence that efficiently conveys purpose, freshness criterion, region example, and output fields. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema exists, the description covers return fields well. However, it omits details about the date parameter (must be Friday) and does not mention pagination or limits. While schema covers these, the incomplete region example reduces completeness for a new agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with clear parameter descriptions, but the description gives an example region as 'Boston, MA', which does not match the expected region code format (e.g., 'ca_los-angeles'). This is misleading and could cause incorrect usage. The description adds no other parameter value and contradicts the schema.

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 states it retrieves freshly listed properties under one week on market, distinguishing it from sibling tools like altos_active_listings which likely return all active listings. The verb 'Get' and resource 'freshly listed properties' are specific.

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 provides a clear context (fresh listings under one week) and an example region ('Boston, MA'), but does not explicitly state when to use this tool versus alternatives or exclusions. The implication is strong enough for an agent to infer usage.

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