swsd-mcp

swsd_log_time

Log work time against SolarWinds Service Desk incidents, problems, changes, or releases by specifying object type, record ID, entry description, and minutes.

Instructions

Log time against a SWSD incident, problem, change, or release. Required: object_type, id, name, minutes_parsed. WRITE — honors SWSD_WRITE_MODE and does not retry on transient failure.

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": {
      "object_type": "<object_type>",
      "id": "<id>",
      "name": "<name>",
      "minutes_parsed": "<minutes_parsed>"
    },
    "name": "swsd_log_time"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Parent record id.
`name`	Yes	Time entry description.
`object_type`	Yes	Parent SWSD object type.
`minutes_parsed`	Yes	Number of minutes to log. SWSD field name is minutes_parsed.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv3.0.0Oct 4, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed1 schema field changedv2.3.1Aug 22, 2026
- addedInput schema / properties / name / maxLength
```
Added value: +2000
```
Addedv2.2.0Jul 9, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false and non-idempotent, so the write nature is partly redundant, but the description adds genuinely useful behavioral context beyond the structured fields: it honors SWSD_WRITE_MODE and does not retry on transient failure. That retry/write-mode disclosure is valuable for an agent deciding how to handle failures. It stops short of stating what gets returned or created.

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?

Three tight sentences with the action, required inputs, and write/retry semantics all front-loaded. No 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?

For a write tool with no output schema and 100% schema coverage, the description covers purpose, target object types, required params, and write-mode/retry behavior. It does not indicate what the call returns (e.g. a created time-track id), but that is a minor gap given the otherwise complete disclosure.

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?

Schema description coverage is 100%, and all four parameters are documented in the schema, so the description's listing of required fields adds little. The schema itself clarifies that minutes_parsed is the SWSD field name and that id is the parent record id, so baseline 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?

States a specific verb+resource ("Log time against a SWSD incident, problem, change, or release") and scopes the exact object types targeted. The verb "log" is clearly distinct from sibling read/update operations like swsd_list_time_tracks and swsd_update_time_track, so an agent can select it without opening the schema.

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?

The description implies when to use it (to log/append time entries against one of four parent object types) and enumerates every required parameter. However, it never contrasts this tool with the alternatives (e.g. swsd_update_time_track for modifying an existing entry), leaving that routing to inference.

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

Deploy Server