Skip to main content
Glama
Sign In
SyncroMSP MCP Server

SyncroMSP MCP Server

by advenimus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

tickets_remove_line_item

Remove a line item from a ticket after confirming the removal. Requires explicit user confirmation to execute.

Instructions

Remove a line item from a ticket. The user MUST confirm before executing this.

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>",
      "ticket_line_item_id": "<ticket_line_item_id>",
      "confirmed": "<confirmed>"
    },
    "name": "tickets_remove_line_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTicket ID
confirmedYesMust be true to confirm removal
ticket_line_item_idYesLine item ID to remove

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the burden. It discloses the confirmation requirement, but lacks details on irreversibility, permissions, or side effects of removal. The confirmation note adds value beyond the schema.

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 concise sentences: first states the action, second states the critical usage condition. No redundant or extraneous information.

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?

Given the operation's complexity (removal with confirmation) and no output schema, the description provides the essential confirmation requirement but omits details like return value, error conditions, or prerequisites (e.g., ticket status).

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%, so the schema already documents all parameters. The description reinforces the confirmed parameter's purpose but does not add new meaning beyond the schema descriptions.

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 'Remove a line item from a ticket,' which is a specific verb+resource. It distinguishes from sibling tools like tickets_add_line_item and tickets_update_line_item by focusing on removal.

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 explicitly states 'The user MUST confirm before executing this,' providing a clear usage condition. However, it does not explicitly compare with alternatives or specify when not to use (e.g., if only updating is needed).

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