Skip to main content
Glama

Message booking client

message_booking_client

Send a message to the clients on a booking.

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": {
      "booking_id": "<booking_id>"
    },
    "name": "message_booking_client"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNo
booking_idYes
business_idNoThe id of the business to act on, from list_businesses. Optional when this connection covers a single business.
attachment_nameNo
attachment_data_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false and openWorldHint=true, so the agent already knows this is a non-read operation with external effects. The description adds nothing about that reach: it does not say the message goes to real people, whether it is email or SMS, whether it is logged, or whether it is retractable once sent. For an outward-facing send action, that is a meaningful gap beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with no filler, so it is not bloated. However, its brevity comes at the cost of substance rather than being earned efficiency — it is under-specified rather than tight.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Five parameters with 20% coverage, no output schema, and an outward-facing side effect make this a case where the description needed to carry weight. It provides only the barest statement of intent, leaving the agent without enough to call it confidently or predict what happens after sending.

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

Parameters2/5

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

Schema description coverage is only 20%, with five parameters and only business_id documented in the schema. The description does not explain the message content (body), the attachment_name/attachment_data_url pairing, or how attachment data must be encoded, so it fails to compensate for the low coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Send a message to the clients on a booking" gives a specific verb (send a message) and a specific resource scope (clients attached to a booking), so an agent can tell what it does. It does not distinguish itself from other potential communication paths or clarify the delivery channel, but with no sibling messaging tools present the intent is legible.

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

Usage Guidelines2/5

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

The description offers no when-to-use guidance, no prerequisites, and no alternatives. It never says whether this is for transactional updates, reminders, or broadcasts, nor whether the booking must be in a particular state before messaging its clients.

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