SyncroMSP MCP Server

products_create_serial

Assign a unique serial number to a product for inventory or warranty tracking. Requires product ID and serial number; optionally set cost and condition.

Instructions

Create a serial number for a product

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": {
      "product_id": "<product_id>",
      "serial_number": "<serial_number>"
    },
    "name": "products_create_serial"
  }
}

Input Schema

Name	Required	Description
`condition`	No	Condition
`product_id`	Yes	Product ID
`serial_number`	Yes	Serial number (required)
`price_cost_cents`	No	Cost in cents
`price_retail_cents`	No	Retail in cents

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1May 26, 2026

TDQS

B3.1/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 carry the full burden. It does not disclose any behavioral traits such as uniqueness constraints, error conditions, or effects on existing data. For a creation tool, more transparency is needed.

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 concise (one sentence, 7 words). However, it lacks structure such as bullet points or sections. It could be expanded slightly without losing conciseness.

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?

With 5 parameters, no output schema, and no annotations, the description is too brief. It does not mention required parameters, expected behavior on duplicate serial numbers, or response format. More context is needed for a creation tool.

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 baseline is 3. The description adds no additional meaning beyond what the input schema provides. It does not explain parameter relationships or formats.

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 verb 'Create' and the resource 'serial number for a product'. It distinguishes from sibling tools like 'products_create' (creating a product) and 'products_create_sku' (creating a SKU).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs alternatives. Sibling tools include 'products_attach_serial_to_line_item' and 'products_update_serial', but the description does not differentiate usage or provide prerequisites.

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

Deploy Server