Skip to main content
Glama
synology-mcp
by r03eRt

Task status

get_task_status
Read-only

Checks the progress and status of a background task using its task ID and type, so you can track long-running copy, delete, compress, extract, size, or MD5 operations.

Instructions

Check progress of a background task that was still running when a previous tool returned its task id.

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": {
      "task_type": "<task_type>",
      "taskid": "<taskid>"
    },
    "name": "get_task_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskidYes
task_typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

B3.4/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 this is a follow-up to a prior tool call, which is useful context, but says nothing about polling cadence, whether task ids expire, or what happens for completed/unknown ids.

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 sentence that is front-loaded with the action and free of filler. Nothing could be removed without losing meaning.

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

Completeness2/5

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

There is no output schema, so the description should describe what progress actually looks like (percentage, state, completion flag), and it does not. Combined with the unstated task_type semantics, the definition is too thin for a two-required-parameter status tool.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry the parameter burden, but it only explains taskid loosely as an id from a previous tool. The required task_type enum (copy_move, delete, compress, extract, dir_size, md5) is completely unaddressed, leaving the agent to guess which value pairs with which originating tool.

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 pairs a specific verb ('Check progress') with a specific resource ('a background task'), and adds the origin condition (a previous tool returned its task id). It does not explicitly distinguish itself from the sibling list_background_tasks, so it stays short of a 5.

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 states the triggering context clearly: use this when a prior tool handed back a task id because the work was still running. That is actionable when-to-use guidance, but it names no exclusion or alternative (e.g. listing all tasks), leaving the agent to infer how to discover tasks it has no id for.

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