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 with consent so the locator can follow up 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

Name	Required	Description
`city`	No	Metro the question concerns.
`agent`	No	Name of the referring assistant/product.
`contact`	No	The renter's phone/email, supplied with their consent. Strongly recommended; otherwise immediately share contact_capture_url returned by this tool.
`question`	Yes	The question for the human locator — specifics beat generalities.
`apartments`	No	Buildings the question is about.

Output Schema

Name	Required	Description	Default
`status`	Yes
`guidance`	No
`next_step`	No
`question_id`	Yes
`contact_status`	No
`contact_capture_url`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 5, 2026

changedInput schema / properties / contact / description

Previous value: -"The renter's phone/email — strongly recommended: the answer is texted/emailed to them directly, and polling alone can strand it."New value: +"The renter's phone/email, supplied with their consent. Strongly recommended; otherwise immediately share contact_capture_url returned by this tool."

addedOutput schema / properties / contact_capture_url
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / contact_status

Added value: +{
+  "enum": [
+    "contactable",
+    "anonymous"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / next_step
```
Added value: +{
+  "type": "string"
+}
```

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.4/5.0

Behavior5/5

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

Adds substantial behavior beyond the annotations: reply timing (Central Time business hours, usually within a few hours), rate limiting, the point-in-time nature of answers, and the warning that agent sessions end so polling alone can strand an answer. This is exactly the operational context annotations can't convey.

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?

Front-loaded with the core purpose, then escalates to the critical contact/consent guidance and rate-limit note. Dense but every clause carries information; the parenthetical about sessions ending is slightly verbose but earns its place.

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?

An output schema exists so return values needn't be explained, yet the description still flags the question_id channel. Combined with timing, rate limits, and consent guidance, an agent has everything needed to invoke this 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 schema already documents all five parameters. The description reinforces the consent requirement for contact and that specifics beat generalities for question, but adds no syntax or format detail beyond the schema — baseline 3 applies.

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?

States a specific verb+resource (ask a question to a human locator) and sharply scopes it with 'only a human can answer', plus concrete example questions. It also implicitly distinguishes itself from the polling sibling by noting it returns a question_id for check_answer.

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?

Gives clear context for when to use it (real-time, human-only facts like current specials and availability) and operational guidance (batch related questions, rate limited, contact strongly recommended). It does not explicitly state when NOT to use it or name request_locator_help as an alternative, so it stops short of a 5.

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?