Skip to main content
Glama
stornoro

Storno CLI

by stornoro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

import_execute

Execute a confirmed import job asynchronously via message queue; monitor with import_get.

Instructions

Execute an import job after mapping is confirmed. The import runs asynchronously via a message queue. Check status with import_get.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesImport job ID
companyIdNoCompany UUID override (uses active company if not set)
importOptionsNoOptional import options: markAsPaid (invoice imports); groupBy = week | day | order and platformName / platformCif / platformCountry (platform_sales); includeAll to import orders whose status is not paid / completed (WooCommerce, PrestaShop); cashRegisterName, vatGroups ({"1": "21", "2": "11", "3": "5", "4": "0"}) and paymentTypes ({"1": "cash", "3": "card"}) for receipts

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.48
    • changedInput schema / properties / importOptions / description
      Previous value: -"Optional import options (e.g., skipDuplicates, updateExisting)"New value: +"Optional import options: markAsPaid (invoice imports); groupBy = week | day | order and platformName / platformCif / platformCountry (platform_sales); includeAll to import orders whose status is not paid / completed (WooCommerce, PrestaShop); cashRegisterName, vatGroups ({\"1\": \"21\", \"2\": \"11\", \"3\": \"5\", \"4\": \"0\"}) and paymentTypes ({\"1\": \"cash\", \"3\": \"card\"}) for receipts"
  2. First observedv1.0.17

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that execution is asynchronous via a message queue and points to import_get for status. It does not mention re-run behavior, failure effects, or what the call returns, which is meaningful for a mutation-like tool.

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 sentences with no wasted words. The action and precondition are front-loaded, and the async-status pointer is placed immediately after.

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?

Given no output schema and no annotations, the description provides the key workflow context: execute after mapping, run asynchronously, and check status via import_get. It omits return-value behavior and failure semantics, but the essential knowledge for calling the tool is present.

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%, including detailed descriptions for importOptions subfields. The description itself adds no parameter-level meaning, so the baseline of 3 is appropriate.

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 uses a specific verb ('Execute') with a clear resource ('import job') and an explicit precondition ('after mapping is confirmed'). This distinguishes it from nearby siblings like import_mapping, import_preview, and import_upload.

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 clearly states when to use the tool: after mapping is confirmed. It also directs the caller to import_get for status follow-up. However, it does not explicitly say when not to use it or compare it with alternatives like import_preview or import_mapping.

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

Deploy Server

Other Tools