Claude Orchestrator MCP

Get Pending Sync Points

get_pending_sync_points

Retrieve all pending sync point requests involving your session. Coordinates multiple Claude Code sessions by showing requests awaiting your action.

Instructions

Get all pending sync point requests that involve your 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": {
      "sessionId": "<sessionId>"
    },
    "name": "get_pending_sync_points"
  }
}

Input Schema

Name	Required	Description	Default
`sessionId`	Yes	Your session ID

Output Schema

Name	Required	Description	Default
`syncPoints`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 13, 2026

TDQS

B3.1/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 burden. It implies a read via 'Get' but says nothing about whether fetching consumes or acknowledges the pending requests, whether it blocks/waits, or any rate limits. Output schema covers return values, but the interaction semantics remain undisclosed.

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?

A single, front-loaded sentence with the resource and scope stated immediately and no wasted words.

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 return shape is covered by the output schema and the single parameter is fully documented, so the definition is callable. However, with no annotations the description should have clarified read-only semantics and whether this is a polling operation that leaves requests pending.

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?

Only one parameter exists and schema description coverage is 100%, so the schema already documents sessionId fully. The description adds no syntax or format detail beyond what the schema provides, 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?

States a specific verb (Get) and a specific resource (pending sync point requests) scoped to 'your session', which is clear and actionable. It does not explicitly differentiate itself from siblings like get_cross_project_updates or request_sync_point, so it falls short of a 5.

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?

There is no guidance on when to call this versus alternatives such as get_cross_project_updates or acknowledge_sync_point, nor any prerequisite (e.g. must a session be registered first). Usage is only loosely implied by the phrase 'pending ... that involve your session'.

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

Deploy Server