Skip to main content
Glama

Migawari

Send a message to the operator

send_message

Send a message to the human operator about a quote or task. The operator's replies appear in the messages of get_task_status.

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": {
      "id": "<id>",
      "access_token": "<access_token>",
      "message": "<message>"
    },
    "name": "send_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
messageYesPlain text, 1-2000 characters.
access_tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description adds genuinely new behavioral information — the recipient is a human, the interaction is asynchronous, and the reply channel is the message stream of get_task_status. It stops short of saying whether delivery is immediate, whether messages can be retracted, or any rate limits, so it is not fully transparent.

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

Conciseness5/5

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

Two short sentences with zero filler, and the core action is front-loaded before the reply-routing detail.

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

Completeness3/5

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

For a three-parameter mutation with no output schema, the description covers the purpose and the reply path but omits the identity of the required 'id', the meaning of the required access_token, and any confirmation of what a successful send returns. Those gaps matter more here because the schema supplies almost nothing.

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?

Only the 'message' parameter carries schema documentation (1-2000 chars plain text), leaving 'id' and 'access_token' at 33% coverage. The description never clarifies what 'id' identifies (task id, quote id, conversation id) even though the ambiguity is central to calling the tool correctly.

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 ('Send a message to the human operator') plus a scope ('about a quote or task'), so the agent knows exactly what action it performs. It also distinguishes itself implicitly from get_task_status by noting that replies come back there, though it never explicitly frames that as the read-side counterpart.

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 'about a quote or task' gives a rough usage context and the second sentence tells the agent where to look for replies, which is useful routing guidance. However, there is no explicit when-to-use/when-not-to-use rule and no mention of anything it should be preferred over.

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.