Claude Orchestrator MCP

Notify Related Sessions

notify_related_sessions

Notify all related project sessions of significant changes, affected files, and recommended actions.

Instructions

Broadcast a notification to all related sessions in your project group. Use this when you make significant changes that others should know about.

Input Schema

TableJSON Schema

Name	Required	Description
`summary`	Yes	Brief description of the change
`sessionId`	Yes	Your session ID
`changeType`	Yes	Type of change
`affectedFiles`	Yes	List of affected files
`recommendedActions`	No	Suggested actions for recipients

Output Schema

TableJSON Schema

Name	Required	Description	Default
`notified`	Yes
`sessionIds`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 13, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. It implies a one-to-many write/broadcast with side effects, but omits permissions, delivery guarantees, rate limits, and reversibility.

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 sentences, front-loaded with purpose and then usage. No redundant or wasted language.

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?

Given 100% schema coverage and an output schema, the description does not need to explain fields or return values. It gives purpose and usage context, though it could note behavioral constraints since no annotations exist.

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 already documents all five parameters. The description adds no parameter-level meaning beyond the schema, making the baseline of 3 appropriate.

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 ('Broadcast a notification to all related sessions') and scopes it to 'your project group'. It does not reference sibling tools, but the broadcast action is clearly distinct from list, get, and request tools in the sibling set.

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?

Provides a clear condition for use ('when you make significant changes that others should know about'). It does not state when not to use the tool or name alternative approaches, so it stops short of full guidance.

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

Deploy Server