Skip to main content
Glama
Sign In
SyncroMSP MCP Server

SyncroMSP MCP Server

by advenimus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

invoices_delete

Permanently delete an invoice after user confirmation. Requires invoice ID and explicit confirmation to avoid accidental removal.

Instructions

DELETE an invoice permanently. The user MUST confirm.

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

Input Schema

NameRequiredDescriptionDefault
idYesInvoice ID
confirmedYesMust be true to confirm deletion

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.1/5.0
Behavior3/5

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

The description notes the permanent and destructive nature of the action and the required confirmation, but lacks details on side effects, error conditions, or permissions needed.

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 sentences with no filler; the verb and resource are first, making it immediately clear what the tool does.

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 simple delete with 2 parameters, the description is adequate but could be improved by noting irreversibility, expected response, or prerequisite conditions.

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

Parameters4/5

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

The description adds context beyond the schema by emphasizing the confirmation requirement ('the user MUST confirm'), which reinforces the role of the 'confirmed' parameter.

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 'DELETE an invoice permanently' with a specific verb and resource, distinguishing it from siblings like invoices_update or invoices_delete_line_item.

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 includes the crucial guideline that the user must confirm deletion, but does not explicitly state when not to use this tool or mention alternatives like archiving.

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