Taco Street Locating

Get apartment details

get_apartment_details

Read-onlyIdempotent

Full fact sheet for one building: floorplan-level pricing with as-of dates, move-in costs (admin/application/parking/pet fees), last-known specials (dated — treat as last-known, not current), amenities, walkability, virtual tour. Use the EXACT name from search_apartments. Compute totals yourself from components; a free human locator confirms live numbers.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`city`	No	Metro, to disambiguate same-named buildings.
`name`	Yes	Exact building name from search_apartments.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`city`	Yes
`name`	Yes
`pets`	No
`address`	No
`pricing`	Yes
`building`	No
`guidance`	Yes
`specials`	No
`neighborhood`	No
`move_in_costs`	No
`lifestyle_tags`	No
`taco_street_take`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 8, 2026

addedInput schema / properties / city / description

Added value: +"Metro, to disambiguate same-named buildings."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "address": {
+      "type": "string"
+    },
+    "building": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "city": {
+      "type": "string"
+    },
+    "guidance": {
+      "type": "string"
+    },
+    "lifestyle_tags": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "move_in_costs": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "name": {
+      "type": "string"
+    },
+    "neighborhood": {
+      "type": "string"
+    },
+    "pets": {
+      "type": "string"
+    },
+    "pricing": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "specials": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "taco_street_take": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "name",
+    "city",
+    "pricing",
+    "guidance"
+  ],
+  "type": "object"
+}

AddedSep 8, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already establish readOnly, idempotent, and non-destructive behavior. The description adds valuable behavioral context by flagging specials as last-known and dated, requiring the agent to compute totals itself rather than trust an already-calculated number, and noting that a human locator can confirm live figures.

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?

Three dense sentences deliver the tool's scope, data freshness caveat, and usage rule without wasted words. Key information is front-loaded in the opening clause, and every sentence adds operational value.

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 fully covers what the tool returns, how to call it correctly, and important caveats about data freshness and total calculation. With a rich output schema, read-only annotations, and clear sibling context, nothing essential is missing for an agent to invoke this tool effectively.

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 coverage is 100%, so the schema already documents name and city well, including the disambiguation purpose for city. The description reinforces using the exact name from search_apartments, which is helpful but largely redundant with the schema's parameter descriptions.

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 states a specific action: retrieving a full fact sheet for one building, and lists the concrete contents (floorplan pricing, move-in costs, specials, amenities, walkability, virtual tour). This clearly distinguishes it from search_apartments and the locator sibling tools.

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 gives clear usage context: use the exact name from search_apartments, implying this tool is for follow-up detail lookup on a known building. It does not explicitly enumerate when not to use it, but it does route total confirmation to a human locator, which helps with alternative selection.

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

All Taco Street Locating tools Inspect

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

Need Help?