Taco Street Locating

Ask a human locator

ask_a_locator

Ask a question only a human can answer — current specials, real availability, lease flexibility, 'is the pool actually open'. A human locator replies during Central Time business hours, usually within a few hours. STRONGLY include the renter's contact: the answer is texted/emailed to them directly (agent sessions end; polling alone can strand an answer). Returns a question_id for check_answer as a bonus channel. Rate limited; batch related questions into one. Answers are point-in-time facts.

Input Schema

TableJSON Schema

Name	Required	Description
`city`	No	Metro the question concerns.
`agent`	No	Name of the referring assistant/product.
`contact`	No	The renter's phone/email — strongly recommended: the answer is texted/emailed to them directly, and polling alone can strand it.
`question`	Yes	The question for the human locator — specifics beat generalities.
`apartments`	No	Buildings the question is about.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`status`	Yes
`guidance`	No
`question_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 8, 2026

addedInput schema / properties / city / description
```
Added value: +"Metro the question concerns."
```

addedInput schema / properties / question / description

Added value: +"The question for the human locator — specifics beat generalities."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "guidance": {
+      "type": "string"
+    },
+    "question_id": {
+      "type": "string"
+    },
+    "status": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "question_id",
+    "status"
+  ],
+  "type": "object"
+}

Changed1 schema field changedSep 8, 2026

changedInput schema / properties / contact / description

Previous value: -"Optional: the renter's phone/email so the answer reaches them directly too."New value: +"The renter's phone/email — strongly recommended: the answer is texted/emailed to them directly, and polling alone can strand it."

First observedSep 7, 2026

TDQS

A4.5/5.0

Behavior5/5

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

With all annotations false, the description carries the full behavioral disclosure burden. It reveals asynchronous reply timing, business-hours availability, direct delivery to the renter, the risk of polling-only answers being stranded, rate limiting, and the fact that answers are point-in-time facts. This is substantial and actionable transparency beyond the schema.

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 compact and front-loaded, leading with purpose, then examples, then operational guidance. Every sentence adds value: business hours, contact necessity, return channel, rate limiting, and point-in-time caveat. There is no fluff or repetition of schema mechanics.

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 is complete for an async human-question tool: it explains how answers are delivered, what the agent gets back, when responses occur, and what to do about rate limits. Since an output schema exists and the input schema is fully documented, an agent has everything needed to invoke the tool correctly.

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 baseline is 3. The description reinforces the contact parameter's importance and adds 'batch related questions into one,' but it does not substantially add parameter-level meaning beyond what the schema already provides for question, city, agent, and apartments.

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 opens with a specific verb and resource: 'Ask a question only a human can answer,' backed by concrete examples like specials, availability, and lease flexibility. It clearly separates this tool from automated lookup siblings by emphasizing human-only knowledge, and references check_answer as the companion channel.

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 tells the agent when this tool is appropriate: when the question requires a human, during Central Time business hours, and with a contact included. It also advises batching related questions due to rate limits, but it does not explicitly name alternatives or state when not to use it. The 'only a human can answer' criterion is a clear contextual signal but not a full exclusion list.

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?