Skip to main content
Glama

Send a business a message or booking

send_to_business
Destructive

Start contact with a business on Direct for a message, availability check or booking. Call find_business_agent first; for a business without a card, use call_business. Say an automated assistant is acting, and get the person's permission before booking. A delivered message cannot be recalled. Use the cancel_booking skill only for a booking made through send_to_business, with its booking_id and cancel_token. message_id is the retry key: reuse it unchanged on every retry so the request runs once. If you omit it, an identical request from you counts as a retry only within the same UTC day. Returns the A2A v1.0 {task}: read its state before telling anyone a message was delivered or a booking confirmed. A deposit booking returns INPUT_REQUIRED with a payment_url for the person; it is held 30 minutes and confirmed only after payment, which get_direct_payment checks. Failed, refused and unconfirmed tasks are not charged; costs are in get_m2m_network and your balance in get_direct_usage. Messages and confirmed bookings return thread_id and thread_token: use get_replies to read the business’s replies and reply_to_business to answer in the same conversation. Signed-in requesters may omit callback_number for take_message; anonymous requesters still need their own valid number. Example: biz='harbor-plumbing', skill='take_message', message_id='req-8f2', data={caller_name:'Ana Diaz', callback_number:'+15615550199', need:'Leaking water heater, today if possible'}.

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": {
      "biz": "<biz>",
      "skill": "<skill>",
      "data": "<data>"
    },
    "name": "send_to_business"
  }
}

Input Schema

NameRequiredDescriptionDefault
bizYesThe business id from its card: the <biz> in /b/<biz>/ or /c/<biz>/.
dataYesThe skill's fields; put skill beside data, never inside it. take_message: caller_name, callback_number (the person's own E.164 number, never the business's), need, optional on_behalf_of and urgency (low, normal, high or urgent). check_availability: optional service and date (YYYY-MM-DD in the business's time zone). book: slot exactly as check_availability returned it, caller_name, callback_number, need. book_first_available: options (1 to 5 windows in order, each {date, optional after and before as HH:MM, optional service}), fallback (none or take_message), caller_name, callback_number, need. cancel_booking: booking_id and cancel_token from the confirmed booking, optional reason (up to 300 characters); cancelling is not charged and does not refund a booking fee. For take_message only, a signed-in requester may omit callback_number and receive replies in the thread.
skillYesOne skill the business card lists.
targetNoline (default) for a business line (/b/ card); claim for a claimed listing (/c/ card), which takes messages only.
message_idNoYour id for this request; reuse it unchanged on every retry so the request runs once.
request_idNoRequest opened with open_request; use only for book.
approval_idNoOnly when the business approves bookings itself: the action_id (da_...) from its approval_required reply, sent with the same message_id and data once the owner approves.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / request_id
      Added value: +{
      +  "description": "Request opened with open_request; use only for book.",
      +  "maxLength": 160,
      +  "minLength": 1,
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / data / description
      Previous value: -"The skill's fields; put skill beside data, never inside it. take_message: caller_name, callback_number (the person's own E.164 number, never the business's), need, optional on_behalf_of and urgency (low, normal, high or urgent). check_availability: optional service and date (YYYY-MM-DD in the business's time zone). book: slot exactly as check_availability returned it, caller_name, callback_number, need. book_first_available: options (1 to 5 windows in order, each {date, optional after and before as HH:MM, optional service}), fallback (none or take_message), caller_name, callback_number, need. cancel_booking: booking_id and cancel_token from the confirmed booking, optional reason (up to 300 characters); cancelling is free and does not refund a booking fee. For take_message only, a signed-in requester may omit callback_number and receive replies in the thread."New value: +"The skill's fields; put skill beside data, never inside it. take_message: caller_name, callback_number (the person's own E.164 number, never the business's), need, optional on_behalf_of and urgency (low, normal, high or urgent). check_availability: optional service and date (YYYY-MM-DD in the business's time zone). book: slot exactly as check_availability returned it, caller_name, callback_number, need. book_first_available: options (1 to 5 windows in order, each {date, optional after and before as HH:MM, optional service}), fallback (none or take_message), caller_name, callback_number, need. cancel_booking: booking_id and cancel_token from the confirmed booking, optional reason (up to 300 characters); cancelling is not charged and does not refund a booking fee. For take_message only, a signed-in requester may omit callback_number and receive replies in the thread."
  3. Changed1 schema field changed
    • changedInput schema / properties / data / description
      Previous value: -"The skill's fields; put skill beside data, never inside it. take_message: caller_name, callback_number (the person's own E.164 number, never the business's), need, optional on_behalf_of and urgency (low, normal, high or urgent). check_availability: optional service and date (YYYY-MM-DD in the business's time zone). book: slot exactly as check_availability returned it, caller_name, callback_number, need. book_first_available: options (1 to 5 windows in order, each {date, optional after and before as HH:MM, optional service}), fallback (none or take_message), caller_name, callback_number, need. cancel_booking: booking_id and cancel_token from the confirmed booking, optional reason (up to 300 characters); cancelling is free and does not refund a booking fee."New value: +"The skill's fields; put skill beside data, never inside it. take_message: caller_name, callback_number (the person's own E.164 number, never the business's), need, optional on_behalf_of and urgency (low, normal, high or urgent). check_availability: optional service and date (YYYY-MM-DD in the business's time zone). book: slot exactly as check_availability returned it, caller_name, callback_number, need. book_first_available: options (1 to 5 windows in order, each {date, optional after and before as HH:MM, optional service}), fallback (none or take_message), caller_name, callback_number, need. cancel_booking: booking_id and cancel_token from the confirmed booking, optional reason (up to 300 characters); cancelling is free and does not refund a booking fee. For take_message only, a signed-in requester may omit callback_number and receive replies in the thread."
  4. Changed6 schema fields changed
    • addedInput schema / properties / approval_id / description
      Added value: +"Only when the business approves bookings itself: the action_id (da_...) from its approval_required reply, sent with the same message_id and data once the owner approves."
    • addedInput schema / properties / biz / description
      Added value: +"The business id from its card: the <biz> in /b/<biz>/ or /c/<biz>/."
    • addedInput schema / properties / data / description
      Added value: +"The skill's fields; put skill beside data, never inside it. take_message: caller_name, callback_number (the person's own E.164 number, never the business's), need, optional on_behalf_of and urgency (low, normal, high or urgent). check_availability: optional service and date (YYYY-MM-DD in the business's time zone). book: slot exactly as check_availability returned it, caller_name, callback_number, need. book_first_available: options (1 to 5 windows in order, each {date, optional after and before as HH:MM, optional service}), fallback (none or take_message), caller_name, callback_number, need. cancel_booking: booking_id and cancel_token from the confirmed booking, optional reason (up to 300 characters); cancelling is free and does not refund a booking fee."
    • addedInput schema / properties / message_id / description
      Added value: +"Your id for this request; reuse it unchanged on every retry so the request runs once."
    • addedInput schema / properties / skill / description
      Added value: +"One skill the business card lists."
    • addedInput schema / properties / target / description
      Added value: +"line (default) for a business line (/b/ card); claim for a claimed listing (/c/ card), which takes messages only."
  5. Changed1 schema field changed
    • changedInput schema / properties / skill / enum
      Previous value: -[
      -  "take_message",
      -  "check_availability",
      -  "book",
      -  "book_first_available"
      -]New value: +[
      +  "take_message",
      +  "check_availability",
      +  "book",
      +  "book_first_available",
      +  "cancel_booking"
      +]
  6. Changed1 schema field changed
    • addedInput schema / properties / approval_id
      Added value: +{
      +  "pattern": "^da_[a-f0-9]{24}$",
      +  "type": "string"
      +}
  7. Changed1 schema field changed
    • changedInput schema / properties / skill / enum
      Previous value: -[
      -  "take_message",
      -  "check_availability",
      -  "book"
      -]New value: +[
      +  "take_message",
      +  "check_availability",
      +  "book",
      +  "book_first_available"
      +]
  8. Added

TDQS

A4.8/5.0
Behavior5/5

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

Despite the annotations already flagging a destructive, non-idempotent operation, the description adds substantial behavioral context: delivered messages cannot be recalled, deposit bookings are held for 30 minutes and require payment, and failed or unconfirmed tasks are not charged. It also explains the message_id retry behavior and the return contract for reading task state before confirming delivery or booking.

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?

The description is dense but appropriately structured for a complex, multi-skill tool: it front-loads purpose and prerequisites, then covers safety, retries, returns, payment, costs, thread behavior, and an example. It is not wasteful overall, though the callback_number sentence largely duplicates schema text and could be trimmed.

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 seven-parameter, multi-skill tool with no output schema, the description is complete enough to call correctly. It covers prerequisites, alternative tools, booking permissions, payment behavior, retry semantics, returned thread tokens, and follow-up tools such as get_replies and reply_to_business.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already carries the baseline parameter documentation. The description adds meaningful semantics around message_id as a retry key, including what happens if it is omitted and the same-UTC-day retry boundary, but it also repeats callback_number guidance already present in the schema.

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 and resource: starting contact with a business on Direct for a message, availability check, or booking. It also distinguishes this tool from alternatives by naming find_business_agent and call_business for prerequisites and non-card businesses.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit routing guidance: call find_business_agent first, use call_business when the business has no card, and use cancel_booking only for bookings made through this tool. It also states permission and disclosure requirements before booking, which removes ambiguity about when and how to act.

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