Skip to main content
Glama

send_message_to_operator

Destructive

Send a message from the tourist to a human operator.

Use this when the tourist has a question the AI cannot answer, needs
special arrangements, or explicitly asks to speak with someone.
The operator is notified immediately in the Sóley operator portal.

After sending, automatically call check_operator_replies every 15 seconds
to get the operator's response. Present replies to the user as they arrive.
Requires OAuth2 authentication.

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": {
      "operator_id": "<operator_id>",
      "message": "<message>"
    },
    "name": "send_message_to_operator"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYesThe tourist's message. It is stored and shared with the human operator through the Sóley operator portal.
operator_idYesUnique operator slug, e.g. 'fosshotel-reykjavik'. Obtain from search_operators.
booking_referenceNoOptional booking reference for context.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing that the operator is notified immediately in the Sóley operator portal and that OAuth2 authentication is required – neither of which is in the annotation block. It does not explain the destructiveHint=true / idempotentHint=false pair (e.g., that a sent message is persisted and cannot be recalled or deduplicated), which is the one meaningful behavioral gap for a mutation tool.

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 paragraphs, front-loaded with the action, then eligibility, then the required follow-up. 'Present replies to the user as they arrive' is slightly redundant with the polling instruction, but nothing else is wasted.

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?

An output schema exists so return shape need not be described, and the definition covers auth, notification side effect, and the post-send polling loop. The only omission is any note on irreversibility or duplicate-send behavior, which matters for a non-idempotent, destructive-flagged write.

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 100%, so operator_id, message, and booking_reference are already fully documented including the slug format and the search_operators provenance hint. The description adds no parameter-level meaning beyond that, so the baseline of 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 (send) and resource (message to a human operator) with the direction of communication made explicit ('from the tourist'). The related read tool check_operator_replies is named later, so an agent can separate the send path from the poll path without consulting either schema.

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?

Enumerates concrete triggering conditions: unanswerable question, special arrangements, or an explicit request to speak to a human. It also prescribes the follow-up workflow (call check_operator_replies every 15 seconds and surface replies), which removes any ambiguity about what happens next.

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