tacticalrmm-mcp-server

List TacticalRMM Windows Updates

tacticalrmm_list_win_updates

Read-onlyIdempotent

List Windows Update inventory for a specific agent to check installed patches. Read-only, does not scan or install updates.

Instructions

List Windows Update inventory for an agent from /winupdate/<agent_id>/. This tool is read-only and does not scan or install updates.

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": {
      "agent_id": "<agent_id>"
    },
    "name": "tacticalrmm_list_win_updates"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of items to return.
`offset`	No	Number of items to skip locally after receiving the API response.
`agent_id`	Yes	TacticalRMM agent_id value.
`response_format`	No	Output format: markdown for human-readable summaries, json for structured output.	markdown

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds value by explicitly stating 'does not scan or install updates', which goes beyond the generic read-only annotation and clarifies that this is purely an inventory listing operation. No contradiction with 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?

The description is two concise sentences that are front-loaded with the core action and endpoint. Every sentence earns its place, and there is zero waste or redundancy.

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?

Given the tool's simplicity (list operation, 4 parameters, no output schema), the description is sufficient. It communicates the purpose, endpoint, and the fact that it's non-intrusive. However, a brief note on the return structure (e.g., fields like update title, date) would improve completeness since there is no output schema.

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?

The input schema has 100% description coverage for all four parameters, including defaults and enums. The description does not add any additional parameter-specific meaning beyond what the schema already provides, so the baseline of 3 is appropriate.

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?

The description clearly states the tool's purpose: 'List Windows Update inventory for an agent' with a specific API endpoint. This verb+resource combination distinguishes it from sibling list tools like list_agent_software or list_agent_services, which focus on other aspects of agent inventory.

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 description provides clear context: it is read-only and does not scan or install updates, which implies when it should and should not be used. However, it does not explicitly name an alternative tool for scanning or installing updates, or provide explicit 'when to use' scenarios beyond the read-only note.

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