Taco Street Locating

Request a free human locator

request_locator_help

Idempotent

Hand the renter to Alexander, Taco Street's human locator, who confirms live pricing/availability and books tours — free to renters (properties pay locators). Follow-up arrives by TEXT or EMAIL, never a cold call. Requires the renter's real phone or email, shared with their consent. One request per renter — duplicates within 24h return the existing lead.

Input Schema

TableJSON Schema

Name	Required	Description
`city`	No	Metro the renter is searching (Austin, Dallas or Houston).
`name`	No	The renter's name, if shared.
`note`	No	Anything the locator should know.
`agent`	No	Name of the referring assistant/product.
`contact`	Yes	The renter's phone number or email (with their consent).
`move_in`	No	Move-in timeline, e.g. 'November'.
`bedrooms`	No	Bedroom count the renter needs, e.g. 1BR.
`budget_max`	No	The renter's max monthly rent in USD.
`neighborhoods`	No	Neighborhoods the renter prefers.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`lead_id`	Yes
`message`	Yes
`success`	Yes
`duplicate`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedSep 8, 2026

addedInput schema / properties / bedrooms / description

Added value: +"Bedroom count the renter needs, e.g. 1BR."

addedInput schema / properties / budget_max / description
```
Added value: +"The renter's max monthly rent in USD."
```

addedInput schema / properties / city / description

Added value: +"Metro the renter is searching (Austin, Dallas or Houston)."

addedInput schema / properties / name / description
```
Added value: +"The renter's name, if shared."
```
addedInput schema / properties / neighborhoods / description
```
Added value: +"Neighborhoods the renter prefers."
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "duplicate": {
+      "type": "boolean"
+    },
+    "lead_id": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "success": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success",
+    "lead_id",
+    "message"
+  ],
+  "type": "object"
+}

First observedSep 7, 2026

TDQS

A4/5.0

Behavior5/5

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

The description adds meaningful behavioral detail beyond the annotations: follow-up arrives by text or email, never a cold call; the renter's contact must be shared with consent; duplicates within 24h return the existing lead. This also elaborates the idempotentHint annotation instead of merely repeating it.

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 sentences with no redundancy: first sentence states the action and cost model, second covers communication behavior, third covers consent and deduplication. Every sentence earns its place and the main action is front-loaded.

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?

For a 9-parameter tool with full schema coverage and an output schema, the description covers the essential workflow, consent requirement, contact method, and idempotency behavior. It doesn't describe edge cases like missing optional parameters, but the schema already documents those.

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 already documents all 9 parameters with 100% coverage, so the baseline is 3. The description reinforces that the 'contact' parameter must be real and consent-based, but it doesn't add new meaning to the other parameters.

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 the action ('Hand the renter to Alexander...') and the resource (Taco Street's human locator), so an agent can tell what the tool does. It doesn't explicitly differentiate from the sibling ask_a_locator, which appears to cover a similar domain, so it misses the full 5-point bar.

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 gives useful context: it's free to renters, requires a real contact with consent, and has a 24h deduplication rule. However, it never states when to prefer this tool over ask_a_locator or other siblings, so the usage guidance is implied rather than explicit.

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?