Skip to main content
Glama
advenimus

SyncroMSP MCP Server

by advenimus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

time_list_timers

List and filter ticket timers by ticket, technician, customer, state, or billing status to find running or paused timers for pausing or stopping.

Instructions

List ticket timers across tickets. Filter by ticket, technician, timer state, customer, or derived billing status. Use status 'running' or 'paused' to find a timer to pause or stop.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number
statusNoFilter by timer state: 'running', 'paused', or 'stopped'
user_idNoReturn timers for this technician
ticket_idNoReturn timers for this ticket
customer_idNoReturn timers for tickets belonging to this customer
billing_statusNoFilter by derived billing status: 'non-billable', 'unbilled', 'billed', or 'invoiced'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.10.0
    • addedInput schema / properties / status
      Added value: +{
+  "description": "Filter by timer state: 'running', 'paused', or 'stopped'",
+  "type": "string"
+}
    • addedInput schema / properties / ticket_id
      Added value: +{
+  "description": "Return timers for this ticket",
+  "type": "number"
+}
    • addedInput schema / properties / user_id
      Added value: +{
+  "description": "Return timers for this technician",
+  "type": "number"
+}
  2. First observedv0.1.1

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. 'List' clearly implies a non-mutating read, and it explains that billing_status is a derived filter, but it says nothing about pagination (despite a page parameter), result volume, or permissions. For a read-only list tool the missing context is modest, hence a middle score.

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?

Three compact sentences, front-loaded with the core action and then the filter dimensions and the workflow use case. No padding, though the filter enumeration slightly overlaps what the schema already states.

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 six-parameter, all-optional list tool with no annotations and no output schema, the description covers what it does and the main filters but omits pagination/return behavior and relationships to the sibling timer-mutation tools. Adequate but not thorough.

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 every parameter is already documented in the schema, and the baseline is 3. The description's enumeration of filter dimensions (ticket, technician, timer state, customer, billing status) mirrors the schema almost exactly; its only added value is clarifying that billing status is 'derived'.

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?

States a specific verb and resource ('List ticket timers') with scope ('across tickets'), so the agent knows this is a read/list operation. It does not, however, distinguish itself from the closely named sibling time_list_timelogs, which an agent could easily confuse it with.

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 gives a concrete usage scenario: filter by status 'running' or 'paused' to locate a timer that needs to be paused or stopped, tying it to the pause/stop siblings. It stops short of naming time_list_timelogs as the alternative for time-entry logs, so routing is clear but not fully disambiguated.

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