MCP E-commerce Server

Add Product (Smart AI Enhanced)

add_product_smart

Create a new e-commerce product and automatically generate an AI description when none is provided. Use it to add catalog items with SKU, name, price, and quantity.

Instructions

Create a new product with smart ai generated description if missing

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 11, 2026

TDQS

A3.7/5.0

Behavior4/5

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

With no annotations, the description carries the full burden of explaining behavior. It discloses the key non-obvious trait: a missing description will be AI-generated. It does not discuss failure modes or side effects, but the core create behavior is transparent.

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?

A single sentence that front-loads the action and then adds the key qualifier. There is no filler or redundant content.

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?

The tool is simple and an output schema exists, but the description does not differentiate add_product_smart from add_product or clarify behavior when a description is actually supplied. These are meaningful gaps for a tool with no annotations.

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 adds meaning for the description parameter by stating it is optional and auto-generated when missing, but the other parameters (sku, name, price, quantity) rely on their self-explanatory names without additional context.

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 clearly states the action ('Create a new product') and the distinguishing behavior ('smart ai generated description if missing'). It does not explicitly contrast with the sibling add_product tool, 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 Guidelines3/5

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

The phrase 'if missing' implies that this tool is useful when a description is not provided, which is a light usage cue. However, it never mentions alternatives like add_product or explains when the plain version should be preferred.

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

Deploy Server