Claude Orchestrator MCP

Request Sync Point

request_sync_point

Coordinate a change across multiple Claude sessions by requesting a synchronization point. Specify a reason, blocking behavior, and required sessions to acknowledge before proceeding.

Instructions

Request a synchronization point with related sessions. Use this when you need to coordinate a change across multiple services.

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": {
      "sessionId": "<sessionId>",
      "reason": "<reason>"
    },
    "name": "request_sync_point"
  }
}

Input Schema

Name	Required	Description
`reason`	Yes	Why synchronization is needed
`blocking`	No	If true, other sessions should wait
`sessionId`	Yes	Your session ID
`timeoutMinutes`	No	How long to wait for acknowledgment
`requiredSessions`	No	Specific session IDs that must acknowledge

Output Schema

Name	Required	Description	Default
`status`	Yes
`expiresAt`	Yes
`syncPointId`	Yes
`notifiedSessions`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 13, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It implies coordination across sessions but does not explain blocking semantics, timeout behavior, acknowledgment requirements, side effects, or what happens to other sessions, leaving key operational traits unstated.

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, no filler, and the core action is front-loaded. The second sentence cleanly serves as the usage condition without bloating the definition.

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?

This is a multi-session synchronization tool with no annotations and five parameters including blocking, timeout, and required acknowledgments. While the output schema can cover return values, the description still omits the behavioral coordination model, making it incomplete for invoking the tool correctly in complex scenarios.

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 input schema already documents all five parameters thoroughly. The description adds only the phrase 'with related sessions' and does not supplement blocking, timeout, or required-session semantics beyond the schema, making the baseline 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?

The description names a specific verb and resource: request a synchronization point. It also scopes the resource to related sessions, which separates it from acknowledgement or retrieval siblings, though it does not explicitly name those alternatives.

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 second sentence gives a clear when-to-use condition: coordinating a change across multiple services. It does not state when not to use the tool or name alternative sibling tools, but the context is explicit enough for routing.

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

Deploy Server