Advocate

Query Business Agent

query_business_agent

Ask a registered business's AI advocate a question and get a citation-ready answer plus a referral link. The question and the business's public profile are processed by an AI provider, and the question and answer are recorded to operate the service. Do not enter sensitive personal, medical, payment, or authentication information. Use this for questions about one business's services, hours, policies, or fit.

Input Schema

Name	Required	Description
`slug`	Yes	Business slug identifier
`query`	Yes	The visitor's question about this business
`stage`	No	Optional buyer stage: browsing \| comparing \| committing
`agent_id`	No	Optional self-asserted calling-agent id — used for logging/tuning only, never auth

Output Schema

Name	Required	Description
`answer`	Yes	Plain-text answer grounded ONLY in the business's public profile; a fixed apology sentence when the model was unavailable or over budget
`business`	Yes	The business's display name
`referral_url`	Yes	Signed, tracked link to the business's own website for the user to follow; null when the business lists no website
`business_slug`	Yes	Echo of the slug that was queried

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 24, 2026
- removedOutput schema / properties / referral_url / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / referral_url / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changed1 schema field changedSep 4, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "answer": {
+      "description": "Plain-text answer grounded ONLY in the business's public profile; a fixed apology sentence when the model was unavailable or over budget",
+      "type": "string"
+    },
+    "business": {
+      "description": "The business's display name",
+      "type": "string"
+    },
+    "business_slug": {
+      "description": "Echo of the slug that was queried",
+      "type": "string"
+    },
+    "referral_url": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Signed, tracked link to the business's own website for the user to follow; null when the business lists no website"
+    }
+  },
+  "required": [
+    "answer",
+    "referral_url",
+    "business",
+    "business_slug"
+  ],
+  "type": "object"
+}

Changed6 schema fields changedJul 16, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / agent_id / description

Previous value: -"Optional caller-asserted agent identifier (e.g. 'claude-desktop', 'cursor', 'gpt-agent'). Used to tune the response shape. May be overridden by the x-agent-identity header. Self-asserted only in v1 — not used for auth or rate limiting."New value: +"Optional self-asserted calling-agent id — used for logging/tuning only, never auth"

changedInput schema / properties / query / description

Previous value: -"The user's question about this business"New value: +"The visitor's question about this business"

addedInput schema / properties / query / maxLength
```
Added value: +2000
```

changedInput schema / properties / slug / description

Previous value: -"The business slug identifier (e.g. 'joes-pizza-austin'). Use search_businesses first if you don't know the slug."New value: +"Business slug identifier"

changedInput schema / properties / stage / description

Previous value: -"Optional buyer stage. 'browsing' (default) — exploring options. 'comparing' — weighing alternatives. 'committing' — ready to act. When omitted, the server infers from query verbs (e.g. 'book'/'reserve' → committing)."New value: +"Optional buyer stage: browsing | comparing | committing"

Changed6 schema fields changedJul 12, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

changedInput schema / properties / agent_id / description

Previous value: -"Optional self-asserted calling-agent id — used for logging/tuning only, never auth"New value: +"Optional caller-asserted agent identifier (e.g. 'claude-desktop', 'cursor', 'gpt-agent'). Used to tune the response shape. May be overridden by the x-agent-identity header. Self-asserted only in v1 — not used for auth or rate limiting."

changedInput schema / properties / query / description

Previous value: -"The visitor's question about this business"New value: +"The user's question about this business"

removedInput schema / properties / query / maxLength
```
Removed value: -2000
```

changedInput schema / properties / slug / description

Previous value: -"Business slug identifier"New value: +"The business slug identifier (e.g. 'joes-pizza-austin'). Use search_businesses first if you don't know the slug."

changedInput schema / properties / stage / description

Previous value: -"Optional buyer stage: browsing | comparing | committing"New value: +"Optional buyer stage. 'browsing' (default) — exploring options. 'comparing' — weighing alternatives. 'committing' — ready to act. When omitted, the server infers from query verbs (e.g. 'book'/'reserve' → committing)."

Changed6 schema fields changedJul 12, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / agent_id / description

Previous value: -"Optional caller-asserted agent identifier (e.g. 'claude-desktop', 'cursor', 'gpt-agent'). Used to tune the response shape. May be overridden by the x-agent-identity header. Self-asserted only in v1 — not used for auth or rate limiting."New value: +"Optional self-asserted calling-agent id — used for logging/tuning only, never auth"

changedInput schema / properties / query / description

Previous value: -"The user's question about this business"New value: +"The visitor's question about this business"

addedInput schema / properties / query / maxLength
```
Added value: +2000
```

changedInput schema / properties / slug / description

Previous value: -"The business slug identifier (e.g. 'joes-pizza-austin'). Use search_businesses first if you don't know the slug."New value: +"Business slug identifier"

changedInput schema / properties / stage / description

Previous value: -"Optional buyer stage. 'browsing' (default) — exploring options. 'comparing' — weighing alternatives. 'committing' — ready to act. When omitted, the server infers from query verbs (e.g. 'book'/'reserve' → committing)."New value: +"Optional buyer stage: browsing | comparing | committing"

First observedMay 5, 2026

TDQS

A4.5/5.0

Behavior5/5

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

The description adds critical behavioral context beyond annotations: it discloses that the question and answer are recorded, that an AI provider processes the data, and warns against sensitive information. This is essential for an agent to understand privacy and data handling.

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, each earning its place: first states purpose and output, second discloses data processing, third gives usage guidance and safety warning. Front-loaded and efficient.

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 annotations (readOnlyHint false, openWorldHint true) and an output schema, the description covers necessary behavioral and usage details. Nothing an agent needs to know before calling is missing.

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 each parameter is already documented in the schema. The description does not add any meaning beyond what the schema provides, which is acceptable given the high coverage.

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 (Ask), resource (business's AI advocate), and output (citation-ready answer plus referral link). It clearly distinguishes from sibling tools that handle bookings, payments, and availability.

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?

It provides clear usage context: 'Use this for questions about one business's services, hours, policies, or fit.' It also includes a safety constraint about not entering sensitive information. However, it does not explicitly name when not to use or mention alternative tools.

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

All Advocate 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?