Skip to main content
Glama

escalate_message

Hand off an inbound message to an inbox you control in your workspace, without external sending credits. Botmail delivers the message; you supply the receiving agent, workflow or human team. Delivery does not mean the work is accepted or completed

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": {
      "messageId": "<messageId>",
      "to": "<to>",
      "note": "<note>",
      "operationId": "<operationId>"
    },
    "name": "escalate_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesTarget @botmail.work inbox address in your workspace
noteYesTriage summary / escalation note for the target inbox in your workspace
categoryNoOptional escalation category tag
severityNoEscalation severity (default: normal)
messageIdYesOriginal message ID to escalate
operationIdYesIdempotency key (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, non-open-world write. The description adds genuinely new semantics: no external sending credits are consumed, Botmail handles delivery, and delivery must not be read as acceptance or completion of work. That outcome clarification is valuable context above what annotations provide.

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 core action is front-loaded in the opening clause, and the sentences are tight. The final clause about delivery not meaning acceptance is slightly tangential to conciseness but earns its place as a behavioral caveat.

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?

With six fully documented parameters, no output schema, and clear annotations, the description covers what is needed to call the tool correctly and what the outcome means. Minor gaps remain around what happens on repeated escalation of the same message, but the essentials are present.

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 every parameter including the operationId idempotency key and severity enum is documented in the schema. The description adds nothing about parameter meaning or usage, so baseline 3 applies.

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?

States a specific verb-and-resource pair — hand off an inbound message to an inbox you control — and clarifies the delivery mechanism (Botmail delivers, you supply the receiving destination). This distinguishes it reasonably well from send_message by noting it needs no external sending credits, though it never names that sibling explicitly.

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

Usage Guidelines3/5

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

The phrase 'without external sending credits' implies when to prefer this over send_message, and the closing sentence warns that delivery is not acceptance. But there is no explicit when-to-use/when-not guidance versus reply_to_message, archive_message, or send_message, leaving the routing decision to inference.

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