Skip to main content
Glama

Belline Connect

Ask a business's receptionist

ask_business

Asks a business's own receptionist (Belle) a question and returns her answer: opening hours, emergencies, call-out costs, areas served. She answers only from what the business has told her and says when she does not know, as she does for any customer. The answer carries a conversation_id that continues the same conversation. If the person wants to go ahead she may take their details and pass the request to the business; that is not a booking. The first message tells her an AI assistant is asking for a customer.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>",
      "agent_name": "<agent_name>",
      "message": "<message>"
    },
    "name": "ask_business"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesBusiness slug.
messageYesThe question, in plain language, up to about 600 characters.
agent_nameYesWhich assistant is asking, for example Claude.
conversation_idNoFrom an earlier answer, to continue the same conversation. Leave out to start a new one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: the receptionist answers only from what the business supplied, admits when she does not know, may collect details and forward a request (explaining the non-read-only, non-idempotent hints), and the first message discloses that an AI assistant is asking. Return-shape behavior (answer plus conversation_id that continues the thread) is also covered.

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-loads what the tool does and what it returns, then layers constraints and side effects; nearly every sentence carries information. Slight redundancy in restating conversation_id continuity that the schema already covers.

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?

Complete enough for a four-parameter, no-output-schema tool: it explains the answer content, the conversation continuation mechanism, honesty limits, and the possible request handoff. It does not address failure modes such as an invalid slug or an unreachable business.

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 all four parameters are already documented. The description reinforces conversation_id continuity and the framing role of agent_name but adds no syntax, limits, or format details beyond the schema, so 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 and resource ('Asks a business's own receptionist ... returns her answer') and enumerates the question domains (opening hours, emergencies, call-out costs, areas served). It also explicitly distinguishes the outcome from a booking, which separates it from book_slot/create_inquiry siblings.

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 call: to get answers the business itself has provided, and clarifies 'that is not a booking', steering bookings elsewhere. It never names the concrete alternative tool to use for a real booking, so routing is implied rather than spelled out.

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.

Resources