Skip to main content
Glama

List the sync manifest for a project

file_sync_list

Lists project files with content hashes, sizes, and versions so you can compare local file hashes against content_hash and detect changes.

Instructions

List the files stored for a project with their content hash, size, and version. This is the diff surface: compare your local file hashes against content_hash.

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": {
      "project": "<project>"
    },
    "name": "file_sync_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYesProject to list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

A4/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It implies a read-only operation and discloses returned fields, but does not mention permissions, pagination, ordering, or whether deleted files are included—details that would be valuable for a sync manifest tool.

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 tightly written sentences with zero waste. The purpose is front-loaded, followed by the key usage hint, making it easy to scan and act on.

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 one-parameter list tool with no output schema, the description adequately covers purpose, returned fields, and usage context. It omits pagination and ordering behavior, which are minor gaps for a simple manifest listing.

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 single parameter ('project') is fully documented in the schema. The description reinforces that it applies to a project but adds no syntax, format, or constraint details beyond what the schema already provides, matching the baseline 3 for high coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('List') and resource ('files stored for a project') along with the exact fields returned (content hash, size, version). The phrase 'This is the diff surface' distinguishes it from sibling tools like file_sync_pull, file_sync_prune, and file_sync_put by clarifying its role.

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 sentence 'This is the diff surface: compare your local file hashes against content_hash' gives a clear condition for when to use the tool. However, it does not explicitly name alternatives (e.g., file_sync_pull) or state when not to use it, leaving some inference to the agent.

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

Deploy Server

Other Tools