Skip to main content
Glama

syncthing_pending_folders

Read-only

List folders pending synchronization in Syncthing to monitor sync status and identify items requiring attention.

Instructions

Pending folders.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
cursorNo
fieldsNo
instanceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

D1.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered by structured data. The description adds nothing beyond that — it does not say what a 'pending folder' is, whether it reflects remote offers awaiting acceptance, or that results are paginated.

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

Conciseness2/5

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

Extremely short, but this is under-specification rather than conciseness. The two words do not earn their place because they convey nothing the tool name has not already conveyed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a paginated, multi-param query tool with no output schema and zero schema description coverage, the description is completely inadequate. An agent cannot determine what data is returned, what 'pending' means, or how to use limit/cursor/fields correctly.

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

Parameters1/5

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

Schema description coverage is 0% across four parameters (limit, cursor, fields, instance), so the description would need to compensate. 'Pending folders.' provides no parameter information at all, leaving limit/cursor pagination behavior and the instance selector entirely undocumented.

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

Purpose2/5

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

The description 'Pending folders.' is a bare restatement of the tool name with no verb and no explanation of what 'pending' means in the Syncthing context (folders awaiting an action). It does not distinguish this tool from siblings like syncthing_folders, syncthing_folder_status, or the parallel syncthing_pending_devices.

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

Usage Guidelines1/5

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

No indication of when to use this tool, when not to, or how it relates to alternatives such as syncthing_folders or syncthing_folder_status. The agent has no basis for routing between these sibling tools.

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