SyncroMSP MCP Server

tickets_add_timer

Add a timer entry to a ticket for time tracking. Provide start time or duration to auto-calculate end time.

Instructions

Add a timer entry to a ticket for time tracking. Note: start_at is REQUIRED (API returns 422 without it). duration_minutes auto-calculates end_time from start_at.

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": {
      "id": "<id>"
    },
    "name": "tickets_add_timer"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Ticket ID
`notes`	No	Timer notes
`end_at`	No	End time (ISO 8601)
`user_id`	No	User ID (defaults to current user)
`start_at`	No	Start time (ISO 8601) - REQUIRED
`product_id`	No	Product ID for billing
`duration_minutes`	No	Duration in minutes (alternative to start/end)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1May 26, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Discloses required parameter and auto-calculation behavior. No annotations exist, so description carries full burden; missing details on side effects, permissions, or error handling.

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 efficient sentences with no redundancy, front-loading the core action and key requirement.

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?

Adequate for a simple addition tool with no output schema; could mention return value but not essential.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and description adds critical nuance: start_at is required (despite not marked required) and duration_minutes auto-calculates end_time.

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?

Clearly states 'Add a timer entry to a ticket for time tracking'. Distinguishes from sibling timer tools like update and delete.

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?

Specifies that start_at is required and that duration_minutes auto-calculates end_time. Lacks explicit comparison to sibling tools but provides actionable usage context.

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

Deploy Server