Skip to main content
Glama
Sign In
SyncroMSP MCP Server

SyncroMSP MCP Server

by advenimus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

tickets_charge_timer

Convert a timer entry on a ticket into a billable line item. This action charges the timer entry, making it ready for invoicing.

Instructions

Charge a timer entry on a ticket (convert to billable line item)

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>",
      "timer_entry_id": "<timer_entry_id>"
    },
    "name": "tickets_charge_timer"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTicket ID
timer_entry_idYesTimer entry ID to charge

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It mentions conversion to a billable line item, but lacks details on side effects (e.g., whether the timer is deleted, if it's idempotent, required permissions, or error cases).

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 sentence with no wasted words. It is efficient, though could include slightly more context without becoming verbose.

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

Completeness2/5

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

Given the many related sibling tools (e.g., tickets_add_timer, tickets_add_line_item) and the lack of an output schema, the description does not fully explain the operation's effect or what is returned. It leaves ambiguity about the 'conversion' process.

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 coverage is 100% with descriptions for both parameters ('Ticket ID', 'Timer entry ID to charge'). The description adds no further meaning beyond the schema, so baseline score of 3 applies.

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?

The description clearly states the tool's action: 'Charge a timer entry on a ticket (convert to billable line item)'. It uses a specific verb ('Charge') and resource ('timer entry on a ticket'), distinguishing it from siblings like tickets_add_timer or tickets_delete_timer.

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 usage for converting a timer to a billable item but does not provide explicit when-to-use or when-not-to-use guidance, nor alternatives among sibling tools like tickets_add_line_item or tickets_update_timer.

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