Conecto

Import items from CSV

inventory_import

Items from a CSV in the file store, created or changed by SKU. Columns: sku, name, description, unit, barcode, cost, price, reorder_point, quantity, location (sku and, for new items, name). A quantity sets what is held at the row's location (default Main, made if new): the difference becomes an adjustment, in at the row's cost. All rows or none. Charged per row. Costs $0.001 per row imported; 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": {
      "file_id": "<file_id>"
    },
    "name": "inventory_import"
  }
}

Input Schema

Name	Required	Description	Default
`file_id`	Yes
`max_rows`	No	The most rows this call may import (and hold the price for).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A3.5/5.0

Behavior4/5

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

The annotations already establish that this is a non-read-only, non-idempotent, non-destructive mutation. The description adds substantial behavioral detail beyond that: atomic all-or-none processing, per-row pricing, quantity-adjustment behavior, default location creation, and cost accounting. It does not cover permissions or error modes, but it is much richer than the annotations alone.

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 front-loaded with the core purpose and then moves through columns, quantity behavior, atomicity, and cost. It is dense but mostly purposeful, though the adjacent phrases 'Charged per row' and 'Costs $0.001 per row imported' are 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?

For a complex import operation with no output schema, the description covers the important CSV columns, SKU-based matching, quantity adjustment logic, atomic processing, and pricing. It leaves some gaps around max_rows behavior and result reporting, but is largely complete for an agent to invoke it correctly.

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

Parameters2/5

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

Schema description coverage is only 50%. The required file_id parameter has no description in the schema, and the tool description only indirectly implies a file-store CSV rather than explaining file_id format or behavior. The max_rows parameter is documented in the schema but not discussed in the description, so the description does little to compensate for the coverage gap.

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 a specific verb and resource: importing items from a CSV file in the file store, with rows matched by SKU. It does not explicitly differentiate itself from sibling tools such as inventory_save_items or import_csv, but the CSV/import framing makes its purpose identifiable.

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?

Usage is implied by the CSV file-store context and the SKU-based create-or-change behavior, but the description gives no explicit when-to-use guidance, no exclusions, and no named alternatives such as inventory_save_items for direct item updates.

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?