E-commerce MCP Server

Add Product

add_product

Creates a new product in an e-commerce catalog by specifying SKU, name, price, quantity, and an optional description for inventory management.

Instructions

Create a new product with sku, name, description(optional but better to have), price, and quantity.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`sku`	Yes
`name`	Yes
`price`	Yes
`quantity`	Yes
`description`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	No
`sku`	Yes
`name`	Yes
`price`	Yes
`quantity`	Yes
`created_at`	No
`updated_at`	No
`description`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 15, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It communicates a write operation ('Create') and notes that description is optional, but it does not disclose duplicate-SKU behavior, persistence semantics, permissions, or what happens on invalid input.

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?

The description is a single front-loaded sentence with no filler. It states the action first and compacts the parameter list, including an optionality note, without wasted words.

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?

Although an output schema exists and can cover return values, this is still a mutation tool with no annotations and no guidance on how it differs from add_product_smartly. It omits duplicate handling, failure behavior, and selection context, leaving an agent under-informed for correct invocation.

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 description coverage is 0%, so the description must compensate. It lists all five parameter names and marks description as optional but better to have, which is useful. However, it does not explain semantics such as SKU uniqueness, currency, or quantity constraints, so the compensation is only partial.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with 'Create a new product', a specific verb and resource, and enumerates the key fields. It clearly says what the tool does, but it does not differentiate itself from the sibling add_product_smartly, so it stops short of a 5.

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?

There is no guidance about when to use this tool versus its siblings, especially add_product_smartly, which appears to be an alternate creation path. The description is purely declarative and provides no exclusions, prerequisites, or selection criteria.

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

Deploy Server