Skip to main content
Glama

broadcast

Send messages to all Claude AI instances through Inter-Process Communication for coordinated workflows and information sharing.

Instructions

Broadcast a message to all other Claude instances

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
from_idYesYour instance ID
contentYesMessage content
dataNoOptional structured data

Implementation Reference

  • Core handler for broadcast action in the MessageBroker. Loops through all instance queues (except sender), appends the message to each, persists to database, and returns the count of recipients.
    elif action == "broadcast":
        from_id = request["from_id"]
        message = request["message"]
        count = 0
        
        for instance_id in self.queues:
            if instance_id != from_id:
                msg_data = {
                    "from": from_id,
                    "to": instance_id,
                    "timestamp": datetime.now().isoformat(),
                    "message": message
                }
                self.queues[instance_id].append(msg_data)
                
                # Save to SQLite
                self._save_message_to_db(from_id, instance_id, msg_data)
                
                count += 1
                
        return {"status": "ok", "message": f"Broadcast to {count} instances"}
  • MCP tool handler for 'broadcast'. Validates registration, constructs message, sends 'broadcast' action to the broker via BrokerClient, returns response.
    elif name == "broadcast":
        if not current_session_token:
            return [TextContent(type="text", text="Error: Not registered. Please register first.")]
            
        message = {
            "content": arguments["content"],
            "data": arguments.get("data", {})
        }
        response = BrokerClient.send_request({
            "action": "broadcast",
            "from_id": arguments["from_id"],
            "message": message,
            "session_token": current_session_token
        })
        return [TextContent(type="text", text=json.dumps(response, indent=2))]
  • MCP tool registration for 'broadcast' including name, description, and input schema definition.
        name="broadcast",
        description="Broadcast a message to all other Claude instances",
        inputSchema={
            "type": "object",
            "properties": {
                "from_id": {
                    "type": "string",
                    "description": "Your instance ID"
                },
                "content": {
                    "type": "string",
                    "description": "Message content"
                },
                "data": {
                    "type": "object",
                    "description": "Optional structured data"
                }
            },
            "required": ["from_id", "content"]
        }
    ),
  • Input schema for the 'broadcast' tool defining parameters: from_id (required), content (required), data (optional).
    inputSchema={
        "type": "object",
        "properties": {
            "from_id": {
                "type": "string",
                "description": "Your instance ID"
            },
            "content": {
                "type": "string",
                "description": "Message content"
            },
            "data": {
                "type": "object",
                "description": "Optional structured data"
            }
        },
        "required": ["from_id", "content"]
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action but lacks critical details: whether this requires authentication, how messages are delivered (reliability, latency), if there are rate limits, whether it's idempotent, or what happens on failure. 'Broadcast' implies a write operation affecting multiple instances, but no safety or side-effect information is given.

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 a single, clear sentence with zero wasted words. It's front-loaded with the core action and target, making it immediately scannable and efficient. Every word earns its place by conveying essential purpose without redundancy.

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?

For a tool with no annotations, no output schema, and a mutating action ('broadcast'), the description is incomplete. It doesn't explain what 'broadcast' entails operationally, what the response looks like, error conditions, or how it differs from siblings like 'send'. The agent lacks sufficient context to use this tool safely and effectively.

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 the schema fully documents all three parameters (from_id, content, data). The description adds no additional parameter semantics beyond implying 'content' is the broadcast message. This meets the baseline for high schema coverage but doesn't enhance understanding of parameter usage or constraints.

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?

The description clearly states the action ('broadcast') and target ('to all other Claude instances'), making the purpose immediately understandable. It distinguishes this from point-to-point communication tools like 'send' in the sibling list. However, it doesn't specify what 'broadcast' entails technically (e.g., pub/sub, direct messaging).

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?

No guidance is provided about when to use this tool versus alternatives like 'send' (point-to-point) or 'share_command' (command sharing). The description implies a broadcast scope but doesn't clarify use cases, prerequisites, or exclusions. The agent must infer usage from the name alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jdez427/claude-ipc-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server