Skip to main content
Glama
Sign In
openclaw-tools-mcp

openclaw-tools-mcp

by haliphax-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

sessions_send

Send a message to another OpenClaw session for agent-to-agent communication. Identify the target session with a session key or label.

Instructions

Send a message into another OpenClaw session. Use for agent-to-agent communication. Either sessionKey or label must be provided to identify the target session.

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

Input Schema

NameRequiredDescriptionDefault
labelNoTarget session label
messageYesMessage content to send
sessionKeyNoTarget session key (e.g. agent:openclaw-expert:discord:channel:123456)
timeoutSecondsNoHow long to wait for a response

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the action and identification requirement but omits the response/wait behavior enabled by 'timeoutSeconds' (e.g., whether it returns the other session's reply). This is a notable gap for a messaging tool.

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?

The description is two concise sentences, front-loaded with the primary action and followed by an essential requirement. Every word adds value; no redundancy or filler.

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?

The description adequately covers the core purpose and parameter constraints, but for a tool with no output schema or annotations, it should clarify response/wait behavior, especially given the 'timeoutSeconds' parameter. The absence of this detail leaves the agent uncertain about the tool's return value and blocking nature.

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?

While the schema already describes all parameters, the description adds crucial semantic information: 'Either sessionKey or label must be provided to identify the target session.' This is not reflected in the schema's required list, making it valuable beyond the structured data.

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 action: 'Send a message into another OpenClaw session' and explicitly mentions 'Use for agent-to-agent communication,' which distinguishes it from sibling tools like 'message' that likely target users.

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

Usage Guidelines4/5

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

The description gives clear context ('Use for agent-to-agent communication') and identifies a prerequisite (sessionKey or label required). It does not explicitly mention when not to use, but the stated use case is sufficiently directive.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools