trmm-mcp

trmm_agent_software

Read-onlyIdempotent

Retrieve the installed software inventory for a managed agent, with an optional search filter to locate specific applications.

Instructions

Installed software inventory for an agent.

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": "<agent>"
    },
    "name": "trmm_agent_software"
  }
}

Input Schema

Name	Required	Description	Default
`agent`	Yes
`search`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Sep 4, 2026

TDQS

C2.8/5.0

Behavior2/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds no behavioral detail beyond the resource category itself—no mention of filtering, result shape, pagination, or edge cases. Its marginal contribution to behavioral transparency is minimal.

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

Conciseness4/5

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

The description is a single, front-loaded noun phrase with no filler or redundant wording. It is appropriately short for a simple read-only tool, though the brevity leaves useful details about search and output unstated.

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

Completeness3/5

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

The tool is simple, annotations supply the read-only and idempotent profile, and the core return concept ('installed software inventory') is present. However, with no output schema and no explanation of the optional search parameter, an agent must infer part of the calling behavior.

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 property descriptions are completely absent, so the description needed to clarify both the required 'agent' parameter and the optional 'search' parameter. It only restates that the inventory is for an agent and says nothing about the search parameter's meaning, format, or filtering behavior.

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 clearly indicates the tool returns the installed software inventory for a specified agent. The resource type, 'installed software', is distinct from sibling tools like services, processes, or event logs. It could be improved by using an explicit verb like 'lists', but the intent is unambiguous.

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

Usage Guidelines2/5

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

The description gives no guidance on when to use this tool versus alternatives such as trmm_agent_services, trmm_agent_processes, or trmm_agent_windows_updates. It also provides no exclusions, preconditions, or context that would help an agent choose among the many agent-specific inventory tools.

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