Skip to main content
Glama

Altos

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Altos Pending Sales

altos_pending_sales
Read-onlyIdempotent

Find properties under contract in a region (e.g., "Miami, FL"). Returns address, price, beds, baths, and days pending.

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
pendingsYesProperties under contract
returnedYesNumber of pending sales returned
total_availableYesTotal pending sales 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"
+    },
+    "pendings": {
+      "description": "Properties under contract",
+      "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 pending sales returned",
+      "type": "number"
+    },
+    "total_available": {
+      "description": "Total pending sales in region",
+      "type": "number"
+    }
+  },
+  "required": [
+    "region",
+    "date",
+    "total_available",
+    "returned",
+    "pendings"
+  ],
+  "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",
+    "limit": 25,
+    "region": "ca_94105"
+  }
+]
  3. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds that properties are under contract, but no further behavioral details (e.g., rate limits, authentication) beyond what the schema provides.

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?

The description is a single concise sentence that fronts the purpose. Every part is useful, though it could be slightly more structured.

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 presence of an output schema and comprehensive annotations, the description is mostly adequate. However, the region format mismatch and lack of mention of the date param are minor gaps.

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?

Input schema has 100% description coverage for all 4 parameters. The description adds no additional meaning beyond the schema, so baseline score applies.

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 finds properties under contract in a region, and lists returned fields. While it distinguishes from siblings like altos_active_listings implicitly, it does not explicitly differentiate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs alternatives such as altos_active_listings or altos_new_listings. The example region format in the description ('Miami, FL') contradicts the schema's region code format.

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