Skip to main content
Glama
synology-mcp
by r03eRt

List background tasks

list_background_tasks
Read-only

Monitor File Station background tasks such as copy, move, delete, compress, and extract operations, including their progress.

Instructions

List File Station background tasks (copy, move, delete, compress, extract) and their progress.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that results include progress, but stays silent on whether finished/failed tasks are returned, whether results are paginated or capped, and how long tasks persist — modest added context given zero-cost annotations.

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 front-loaded sentence with the resource first and the covered task types in parentheses. No filler, no repetition of the title, and every clause carries information.

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?

With zero parameters, no output schema, and annotations covering the read-only nature, this is nearly complete. The remaining gap is relational context — how this listing differs from get_task_status and what the listing's scope (active only vs. historical) is.

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 no parameters and the input schema is an empty object, so there is nothing for the description to disambiguate. The baseline of 4 applies; the description correctly adds no parameter noise.

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 (List) and resource (File Station background tasks) and enumerates the task kinds covered (copy, move, delete, compress, extract) plus progress reporting. It does not, however, differentiate itself from the sibling get_task_status, so an agent cannot fully resolve which to call from the description alone.

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?

Usage is only implied: an agent can infer this is the enumeration call for async operations, but there is no explicit when-to-use statement, no mention of when to prefer get_task_status for a single task, and no note on whether completed tasks are included in the listing.

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