Kash.click

Add a department

dept_add

Add a new department (product category) to the catalog. Requires a title. Optional fields include VAT rate (vatID), price, discount, position, department group, and variations.

Input Schema

TableJSON Schema

Name	Required	Description
`price`	No	Default price for free-price items
`stock`	No	Stock quantity override at department level
`title`	No	Department/category display name
`vatID`	No	Default VAT rate ID for this department
`unitID`	No	Unit of measure ID
`position`	No	Display order on keyboard
`shopHide`	No	1 to hide from online shop
`needPrepa`	No	1 if items require kitchen preparation
`discountID`	No	Default discount ID
`eatinvatID`	No	Eat-in VAT rate ID
`shortTitle`	No	Short label for receipt or keyboard
`deptGroupID`	No	Department group this department belongs to
`activityCode`	No	Accounting activity code
`keyboardHide`	No	1 to hide from POS keyboard
`variationID0`	No	Variation type ID for slot 0
`variationID1`	No	Variation type ID for slot 1
`variationID2`	No	Variation type ID for slot 2
`variationID3`	No	Variation type ID for slot 3
`variationID4`	No	Variation type ID for slot 4

TDQS

A3.6/5.0

Behavior3/5

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

Annotations indicate the tool is not destructive and not idempotent, which aligns with a creation operation. The description does not add further behavioral context (e.g., side effects, authorization needs), but the tool's behavior is straightforward and no contradictions are present.

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 brief with two key sentences. It effectively communicates the core purpose and a key requirement (title), though it could be more structured by listing all optional fields or using bullet points.

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?

Given 19 parameters and no output schema, the description covers the essential function but omits details about return values, error scenarios, or how variation fields interact. For a straightforward creation tool, it is minimally adequate.

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% with each parameter having a description. The description adds that title is required (though not enforced in schema) and groups a subset of optional fields, but does not enhance meanings beyond the schema. Baseline 3 applies.

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 action (Add), the resource (department), and clarifies it as a product category. This distinguishes it from sibling tools like dept_edit and dept_delete.

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 description indicates that a title is required and lists some optional fields, but does not explicitly state when to use this tool versus alternatives (e.g., dept_edit for modifications). No context about prerequisites or exclusions is provided.

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

All Kash.click tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0

Disambiguation5/5

Each tool targets a distinct entity or action (account, client, order, product, payment, VAT, etc.), with clear naming like 'account_create' vs 'account_edit' and 'data_list_' prefixed listings. No overlapping purposes detected.

Naming Consistency5/5

All tool names use snake_case and follow a consistent verb_noun pattern (e.g., account_create, client_add, data_list_clients). Even compound names like auth_login_with_otp adhere to this structure.

Tool Count4/5

41 tools is high but justified by the wide scope of a POS/accounting system (accounts, clients, orders, products, payments, VAT, reports). Slightly above the typical range but well-scoped.

Completeness5/5

The tool surface covers CRUD for all major entities (clients, departments, products, VAT, payment modes, orders), plus queries, reports, and authentication. No obvious gaps for a small business management server.

Resources

Need Help?