Taco Street Locating

Create a shareable shortlist

create_shortlist

Turn finalist apartments into a Taco Street link (/my-list?s=...) that opens the renter's saved list with those buildings added — compare, AI Read, and free tour requests live there. Use the EXACT names returned by search_apartments.

Input Schema

TableJSON Schema

Name	Required	Description
`city`	No	Metro, to disambiguate same-named buildings.
`agent`	No	Name of the referring assistant/product.
`apartment_names`	Yes	Exact building names from search_apartments to save to the renter's list.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes
`note`	No
`unmatched`	No
`apartments`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 8, 2026

addedInput schema / properties / apartment_names / description

Added value: +"Exact building names from search_apartments to save to the renter's list."

addedInput schema / properties / city / description

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

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "apartments": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "note": {
+      "type": "string"
+    },
+    "unmatched": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "url",
+    "apartments"
+  ],
+  "type": "object"
+}

First observedSep 7, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The annotations say the tool is not read-only, not idempotent, and not destructive, and the description adds the key behavioral detail: it creates a link that opens the renter's saved list with the buildings added. This adequately communicates the main side effect without contradicting the annotations.

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?

Two sentences with no wasted words. The first sentence front-loads the action and outcome, while the second delivers a critical input constraint. The extra benefits (compare, AI Read, free tour requests) justify their place by clarifying the link's purpose.

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?

Given the 100% schema coverage and the presence of an output schema, the description fully equips the agent to call the tool correctly. It explains the tool's effect, the exact-name requirement, the use case, and the downstream value, leaving no material gap for invocation.

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 description coverage is 100%, so the schema already documents city, agent, and apartment_names. The description reinforces the 'EXACT names from search_apartments' requirement, but that is already present in the schema's apartment_names description, so it adds limited new semantic value.

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 verb ('Turn finalist apartments into a Taco Street link'), names the output artifact, and explains what the link lets users do. It clearly distinguishes this tool from siblings like search_apartments and get_apartment_details.

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 implies the right moment to use the tool: when the user has finalist apartments to save and share. It also directs the agent to use exact names from search_apartments, which is a concrete integration constraint, though it does not explicitly list when not to use it.

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?