Skip to main content
Glama

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

TableJSON Schema
NameRequiredDescriptionDefault
slugYesBusiness slug identifier
queryYesThe visitor's question about this business
stageNoOptional buyer stage: browsing | comparing | committing
agent_idNoOptional self-asserted calling-agent id — used for logging/tuning only, never auth

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
answerYesPlain-text answer grounded ONLY in the business's public profile; a fixed apology sentence when the model was unavailable or over budget
businessYesThe business's display name
referral_urlYesSigned, tracked link to the business's own website for the user to follow; null when the business lists no website
business_slugYesEcho of the slug that was queried

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
      +}
  2. Changed6 schema fields changed
    • 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"
  3. Changed6 schema fields changed
    • 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)."
  4. Changed6 schema fields changed
    • 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"
  5. First observed

TDQS

A4.5/5.0
Behavior5/5

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

The description discloses important behavioral traits beyond the annotations: the question and public profile are processed by an AI provider, the interaction is recorded, and users should avoid entering sensitive personal, medical, payment, or authentication information. This meaningfully supplements the sparse annotation metadata and warns about side effects and privacy.

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 three sentences with no filler: the first states the outcome, the second covers privacy/processing behavior, and the third gives usage guidance. Every sentence earns its place and the key action is front-loaded.

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?

For a tool with an output schema and well-documented parameters, the description provides sufficient context: what the tool does, what it returns, when to use it, what side effects exist, and what information to avoid. An agent selecting or invoking this tool has the essential information it needs.

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 four parameters. The description does not add substantial parameter-level detail, though it does reinforce the nature of the query as a visitor question about a single business. This meets the baseline but does not exceed it.

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 precise verb+resource: 'Ask a registered business's AI advocate a question and get a citation-ready answer plus a referral link.' It clearly scopes the tool to questions about a single business and names the output format, distinguishing it from sibling tools like search_businesses or request_service.

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 explicitly states when to use the tool: 'Use this for questions about one business's services, hours, policies, or fit.' It does not explicitly name sibling alternatives or state when not to use them, but the one-business scope and question-oriented purpose provide clear usage context.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.