Skip to main content
Glama

sync_protocols

Synchronize protocols with peer MCP instances via push, pull, or bidirectional sync, targeting specific instances and resolving pull conflicts with configurable strategies.

Instructions

Synchronize protocols with peer MCP instances. Supports push, pull, or bidirectional sync.

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": {
      "projectDir": "<projectDir>"
    },
    "name": "sync_protocols"
  }
}

Input Schema

NameRequiredDescriptionDefault
directionNoSync direction (default: bidirectional)
projectDirYesAbsolute path to the project directory
protocolIdsNoSpecific protocols to sync (default: all active)
targetInstanceNoSpecific instance ID to sync with (omit for broadcast)
includeInactiveNoInclude inactive protocols in push (default: false)
conflictStrategyNoHow to handle conflicts on pull (default: skip)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden and largely does not meet it. It does not say whether this writes to remote instances, what happens on broadcast to all peers, whether pull can overwrite local protocols, or that conflicts are resolved per a strategy — all of which matter for a network-connected mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, operation stated first, no filler. The second sentence largely duplicates the direction enum, so it is efficient but slightly redundant rather than perfectly load-bearing.

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 six-parameter tool that performs network synchronization with destructive conflict strategies and broadcast targeting, the description is thin. It omits output expectations, conflict handling implications, and scoping behavior of targetInstance, none of which are covered by an output schema or annotations.

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 all six parameters (direction, protocolIds, targetInstance, includeInactive, conflictStrategy, projectDir) are already documented in the schema. The description only restates the direction values already covered by the enum, adding no new meaning.

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 gives a specific verb and resource ('Synchronize protocols') plus the counterpart ('peer MCP instances'), so the operation is immediately identifiable. It does not distinguish itself from siblings like export_protocols or import_protocols, which look adjacent in purpose.

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?

It names the three modes (push, pull, bidirectional) but gives no guidance on when to choose this tool over export_protocols/import_protocols, nor any prerequisites. An agent must infer the selection criteria from the enum alone.

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