Skip to main content
Glama
Sign In
Storno CLI

Storno CLI

Official
by stornoro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

import_execute

Execute an import job after mapping is confirmed; the job runs asynchronously via a message queue, and status can be checked 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

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.2/5.0
Behavior4/5

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

Annotations already declare this as a non-read-only, non-idempotent operation, and the description adds relevant behavior: execution is asynchronous via a message queue and status should be checked with import_get. It does not discuss retries, queue failures, permissions, or rate limits, but it adds meaningful operational context beyond the annotations.

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?

The description is three short sentences with no waste, and the precondition is front-loaded before the asynchronous behavior and status-check routing. Every sentence earns its place.

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 an execute tool with a rich nested input schema and no output schema, the description covers the key calling context: mapping must be confirmed, execution is asynchronous, and status is checked via import_get. It could mention retry/error behavior, but the essential invocation guidance 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?

The input schema has 100% description coverage, including detailed importOptions semantics and the companyId override. The description adds no additional parameter meaning beyond the schema, 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 states a specific verb and resource: execute an import job. It also distinguishes the action from the sibling status-check tool by naming import_get, and it establishes the precondition that mapping must already be confirmed.

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 says to use this after mapping is confirmed and points to import_get for status checks, which gives useful selection context. It does not explicitly list exclusions or name other nearby alternatives such as import_preview or import_mapping, so it stops short of fully prescriptive when/when-not guidance.

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