Skip to main content
Glama
WYRE-AI

superops-mcp

by WYRE-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

superops_tickets_log_time

Log work hours against a ticket by recording quantity in the service item's unit, typically hours. Include notes, billable status, and technician details.

Instructions

Log a worklog entry against a ticket. SuperOps records quantity (not a raw minute count) against the service item's unit — typically hours.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qtyYesQuantity of work in the service item's unit, typically hours, e.g. "1.5"
notesNoDescription of work performed
billableNoWhether the time is billable (default: true)
ticketIdYesThe ticket ID to log the work against
unitPriceNoOverride the service item's unit price
afterHoursNoWhether the work was performed after hours (default: false)
billDateTimeNoWhen the work was performed, ISO 8601 (default: now)
technicianIdNoUser ID of the technician who performed the work (defaults to the API token's user)
serviceItemIdNoService catalog item ID to bill the work against

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv2.0.2
    • addedInput schema / properties / afterHours
      Added value: +{
+  "default": false,
+  "description": "Whether the work was performed after hours (default: false)",
+  "type": "boolean"
+}
    • addedInput schema / properties / billDateTime
      Added value: +{
+  "description": "When the work was performed, ISO 8601 (default: now)",
+  "type": "string"
+}
    • removedInput schema / properties / description
      Removed value: -{
-  "description": "Description of work performed",
-  "type": "string"
-}
    • removedInput schema / properties / duration
      Removed value: -{
-  "description": "Time spent in minutes",
-  "type": "number"
-}
    • addedInput schema / properties / notes
      Added value: +{
+  "description": "Description of work performed",
+  "type": "string"
+}
    • addedInput schema / properties / qty
      Added value: +{
+  "description": "Quantity of work in the service item's unit, typically hours, e.g. \"1.5\"",
+  "type": "string"
+}
    • addedInput schema / properties / serviceItemId
      Added value: +{
+  "description": "Service catalog item ID to bill the work against",
+  "type": "string"
+}
    • addedInput schema / properties / technicianId
      Added value: +{
+  "description": "User ID of the technician who performed the work (defaults to the API token's user)",
+  "type": "string"
+}
    • changedInput schema / properties / ticketId / description
      Previous value: -"The ticket ID"New value: +"The ticket ID to log the work against"
    • addedInput schema / properties / unitPrice
      Added value: +{
+  "description": "Override the service item's unit price",
+  "type": "string"
+}
    • removedInput schema / properties / workType
      Removed value: -{
-  "description": "Type of work (e.g., Remote Support, On-site, Phone)",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "ticketId",
-  "duration"
-]New value: +[
+  "ticketId",
+  "qty"
+]
  2. Addedv1.6.3
  3. Removedv1.6.0
  4. First observedv1.2.5

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that quantity is recorded against the service item's unit (typically hours) rather than raw minutes, which is a non-obvious behavioral trait. However, it omits mutation side effects, permission requirements, and defaults, leaving significant gaps for a write operation.

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?

Two tightly written sentences with zero waste. The core action is front-loaded, followed by a critical nuance about quantity semantics.

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?

For a nine-parameter mutation tool with no annotations and no output schema, the description is fairly thin. It covers the key quantity nuance but does not address side effects, required permissions, or default behaviors that an agent should understand before invoking a write operation.

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%, so the schema already documents all nine parameters. The description reinforces the quantity/unit semantics for qty but adds no new parameter meaning beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 states a specific verb and resource: logging a worklog entry against a ticket. This is clearly distinct from siblings like add_note or update. However, it does not explicitly differentiate itself from those siblings or name the alternative tool for time logging.

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?

There is no explicit when-to-use guidance, no prerequisites, and no mention of alternatives. The context is implied by 'log a worklog entry' but the description does not help an agent decide between this and other ticket mutation tools.

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

Deploy Server

Other Tools