Skip to main content
Glama

Belline Connect

Send a booking request

create_inquiry
Idempotent

Sends a booking request to a business for a person. It does not book anything: the business answers (accepted, proposed another time, or declined) within the time stated in get_business_profile, and the answer is read with get_inquiry_status. A repeated request_id returns the same inquiry.

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>",
      "customer_name": "<customer_name>",
      "preferred": "<preferred>"
    },
    "name": "create_inquiry"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesBusiness slug.
addressNoWhere, if the work is at their address.
urgencyNo
preferredYesWhen they would like it, in words: 'Thursday 14:00 to 16:00'.
agent_nameYesWhich assistant is asking, for example Claude. The business sees this as your own word.
request_idNoYour id for this request, so a retry does not make a second inquiry.
service_idNoA service id from get_business_profile. Optional if you describe the job.
descriptionNoWhat needs doing, in the person's words.
customer_nameYesThe person's name.
customer_emailNoAn email address to reach them. Phone or email is needed.
customer_phoneNoA phone number to reach them, with country code. Phone or email is needed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare openWorldHint, idempotentHint, and non-destructive, so the bar is lower; the description still adds real value by disclosing that the operation is asynchronous and out-of-band, with three possible outcomes and a business-defined deadline. It does not add anything about permissions, failure modes, or what the caller receives back beyond the pointer to get_inquiry_status.

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?

Three short sentences, front-loaded with the core action and the crucial non-booking constraint, with no filler. Slightly dense in the middle sentence, which packs the outcome list and two sibling references together.

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?

For an 11-parameter mutation with no output schema, the description supplies the full lifecycle (send, wait, read status) and idempotency behavior, which is what an agent needs to call it correctly. The one remaining gap is that it never says what value comes back to feed into get_inquiry_status.

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 coverage is 91%, so the schema already documents slug, preferred, request_id, service_id, and the contact fields in detail. The request_id sentence restates what the schema description already says about retries, so the description adds essentially no new parameter semantics. 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 ('Sends a booking request') and immediately draws the boundary that matters most with a sibling: 'It does not book anything.' An agent can tell this apart from book_slot or accept_proposal from the text alone.

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?

Names the follow-up path explicitly (answer read with get_inquiry_status, response window defined by get_business_profile), which gives clear when-and-how context. It does not explicitly route the agent to book_slot for a confirmed time, leaving that one alternative to inference from 'it does not book anything.'

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