Skip to main content
Glama

sync_now

Synchronize your vault data across all connected devices. This tool enables users to immediately update local vault content through the Detour server interface.

Instructions

Sync the person's vault with their other devices now (needs vault:edit).

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": "sync_now"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden. It usefully discloses the required permission scope (vault:edit), which an agent could not infer from structured data, but says nothing about whether the sync is blocking, what happens to conflicting changes, whether it is reversible, or what the call returns.

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 short sentence with the action front-loaded and the permission constraint trailing as a parenthetical. No filler, no restatement of the tool name, and nothing an agent must skim past.

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, no-output-schema, no-annotation tool, the description covers the action and the authorization requirement, which is most of what an agent needs. The remaining gap — sync semantics on conflict and whether the call blocks until completion — is meaningful for an eagerness-to-trigger operation but modest given the tool's simplicity.

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 there is nothing for the description to disambiguate; the baseline of 4 applies. The only argument-like information (the vault:edit permission requirement) is correctly surfaced in prose since it cannot live in an empty schema.

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?

Specific verb plus resource plus scope: 'Sync the person's vault with their other devices' tells an agent exactly what action occurs and on what. It is clearly distinguishable from every listed sibling (host/session/file management), though the description never names an alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The word 'now' implies immediate invocation and the parenthetical '(needs vault:edit)' gives an actionable prerequisite, which is real usage guidance. However there is no statement of when *not* to call it (e.g., an in-progress sync, offline device, no devices paired) or what to do instead, so guidance is implied rather than explicit.

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