Conecto

Add or change items

inventory_save_items

Idempotent

Add stock items or change them, matched by SKU: name, unit (pcs, kg, m...), barcode, cost (the unit cost used when stock comes in without one), selling price, reorder point (inventory.low_stock is sent when the stock falls to it), a new SKU, archived (only with none in stock). Stock itself changes only by moves (inventory_move) or counts (inventory_stocktake). Costs $0.005 per item saved; nothing if none are found.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "items": "<items>"
    },
    "name": "inventory_save_items"
  }
}

Input Schema

Name	Required	Description	Default
`items`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, yet the description still adds real value: per-item pricing ($0.005, nothing if no items found), the side effect that reorder_point triggers inventory.low_stock, and the archived precondition. That is exactly the behavioral context annotations cannot carry.

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?

Front-loaded with the core operation, then field meanings, then constraints and cost. The single long comma-list sentence is dense but every clause conveys a distinct field meaning; nothing is redundant.

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?

One array parameter, no output schema, no enums — the description covers the batch upsert nature, per-field meaning, cost model, and the stock/archived constraints. Only the per-item `description` field and behavior when a SKU is not found (create vs no-op) are left unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the load and does so for cost, unit, barcode, price, new_sku, reorder_point, and archived, including the important cost-vs-selling-price distinction. The gap: the nested `description` field and the `sku` matching semantics are not explained.

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?

States a specific verb pair (add/change), the resource (stock items), and the matching key (SKU), plus enumerates which fields are writable. An agent can distinguish this from inventory_move or inventory_stocktake without reading the schema.

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?

Explicitly routes stock-quantity changes away from this tool to inventory_move and inventory_stocktake, and constrains `archived` to items with no stock. It stops short of spelling out a full when-not matrix, but the key exclusion is stated directly.

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

All Conecto tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?