Skip to main content
Glama

team_sync

Synchronize team memory: pull the teammates' state files, sealed with the team key, merge them into the local project memory, and push the local state sealed the same way; nothing else leaves the machine.

Instructions

Synchronize team memory: pull the teammates' state files, sealed with the team key, merge them into the local project memory, and push the local state sealed the same way; nothing else leaves the machine. Conflicts resolve by the newer updated timestamp. Run this periodically during a session to stay in sync with the team, or at session boundaries.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "team_sync"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.20
  2. Removedv1.1.12
  3. Addedv1.1.7

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses the sealing mechanism (team key), a data-egress guarantee ('nothing else leaves the machine'), and a deterministic conflict rule ('newer updated timestamp'). It omits prerequisites and failure behavior, such as what happens when no team key or peer state exists, keeping it out of 5 territory.

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?

The core operation is front-loaded in the first clause, followed by the privacy guarantee, conflict rule, and usage timing — each sentence earns its place. The opening sentence is dense and run-on, packing pull/merge/push into one clause, which slightly hurts scannability.

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?

For a zero-parameter tool with no output schema, the description covers what the operation does, its side effects (local memory mutation), its privacy boundary, and its conflict semantics. It lacks prerequisite context — e.g. whether team_init must have run first or how errors surface — which is the main remaining gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline of 4 applies. The description correctly frames this as a parameterless operation with no configuration surface, and the lack of options is consistent with that.

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 (synchronize) and resource (team memory) and spells out the three-step mechanics: pull teammates' sealed state files, merge into local project memory, push local state back sealed. That operational detail implicitly separates it from siblings like team_init, team_status, and get_project_state, though no sibling is named explicitly.

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?

It gives concrete timing guidance — 'periodically during a session' or 'at session boundaries' — so an agent knows when to invoke it. It stops short of stating when not to use it or naming a specific alternative for one-way reads (e.g. team_status), so it falls short of a 5.

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