chirak-mcp

add_product

Add products to Chirak inventory by entering name, price, stock, barcode, and category. Ideal for registering items or parsing wholesale invoice data.

Instructions

Add a new product to Chirak inventory. Use this when the user asks to add items, parse wholesale invoices, or register products.

Input Schema

TableJSON Schema

Name	Required	Description
`sku`	No	Stock Keeping Unit code (e.g. 'GMLK-01').
`name`	Yes	Full product title/name (required).
`unit`	No	Unit type: 'Adet', 'Kg', 'Gram', 'Kutu', 'Çift', 'Libre', 'Ons'.
`barcode`	No	EAN-13, QR, or other barcode string.
`category`	No	Product category name (e.g. 'General', 'Giyim', 'Kahve').
`currency`	No	ISO currency code (e.g. 'TRY', 'USD', 'EUR').
`costPrice`	No	Purchase or wholesale cost price (optional, default: 0).
`minimumStock`	No	Low stock alert threshold (default: 5).
`sellingPrice`	Yes	Retail selling price for the product (e.g. 150.0).
`stockQuantity`	No	Initial physical stock quantity (default: 0).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No	Result data payload from Chirak API.
`success`	No	Status of the tool execution.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Sep 10, 2026

TDQS

A3.8/5.0

Behavior2/5

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

Annotations already declare this as mutating (readOnlyHint=false) and non-idempotent. The description adds no behavioral detail beyond creation, such as handling of duplicate SKUs, whether optional fields get defaults, or side effects like inventory changes. It mostly restates the operation indicated by the annotations.

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 short sentences with no filler. The core action is front-loaded, and the second sentence provides useful usage context. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The input schema fully documents parameters, an output schema exists, and annotations cover mutation/non-idempotency. The description adds the key invocation contexts. A slightly more complete version would explicitly mention using update_product for existing products, but the current definition is sufficient for correct selection and calling.

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?

The schema covers all 10 parameters with descriptions, so the description does not need to repeat them. It also does not add extra parameter relationships or constraints beyond the schema, leaving the schema as the primary source of parameter meaning.

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 states a concrete action ('Add... product') and resource ('Chirak inventory'), and the qualifier 'new' clearly separates it from the update_product sibling. The listed use cases reinforce what the operation covers without ambiguity.

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?

It explicitly names trigger situations: 'when the user asks to add items, parse wholesale invoices, or register products.' It does not explicitly say when not to use it or direct the agent to update_product for existing products, but the main contexts are clear.

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

Deploy Server