Skip to main content
Glama
nikan

elorus-mcp

by nikan

create_product

Create a new product or service in the catalog with title, price, and tax settings. Accepts sale_price as a string to avoid floating-point errors.

Instructions

Create a new product or service in the catalog. Monetary values must be strings (e.g. '99.99') to avoid floating-point issues.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeNoProduct code or SKU for internal reference
unitNoUnit of measurement ID (obtain from list_units), e.g. hours, pieces, kg
notesNoInternal notes about this product
taxesNoArray of tax IDs to apply by default on this product (obtain IDs via list_taxes)
titleYesProduct or service name
sale_priceNoDefault selling price before tax as a string, e.g. '99.99'
descriptionNoDetailed description of the product or service
purchase_priceNoDefault purchase/cost price before tax as a string, e.g. '60.00'
Behavior2/5

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

No annotations provided, so description carries full burden. Only mentions monetary string requirement; lacks info on side effects, permissions, idempotency, or return behavior.

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 concise sentences: first states purpose, second provides a critical formatting note. No unnecessary words.

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?

Adequate for a creation tool with 8 parameters; thorough schema descriptions compensate. Lacks a note on what the response contains (e.g., created product ID), but not critical.

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 100%, so baseline is 3. Description reinforces schema for sale_price/purchase_price but adds no new semantic meaning beyond what's already in the schema.

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?

Clearly specifies verb 'Create' and resource 'product or service in the catalog', distinguishing it from sibling tools like create_bill, create_invoice, etc.

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; no prerequisites or context provided for invocation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nikan/elorus-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server