Skip to main content
Glama
Sign In
Storno CLI

Storno CLI

Official
by stornoro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

import_template

Read-onlyIdempotent

Downloads a ready-to-fill CSV template for a chosen import type, with column headers and example rows. Use it to prepare data, then upload via import_upload; pass a platform source to match that export layout.

Instructions

Download a CSV template for a specific import type. Returns base64-encoded CSV with column headers and example rows that can be filled in and uploaded via import_upload. Pass source for a platform or shop template (uber, bolt, glovo, tazz, woocommerce, prestashop) to get the columns of that export instead of the generic ones.

Input Schema

NameRequiredDescriptionDefault
sourceNoPlatform / shop whose column layout the template should use
companyIdNoCompany UUID override (uses active company if not set)
importTypeYesType of import to get template for

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.48
    • changedInput schema / properties / importType / enum
      Previous value: -[
-  "clients",
-  "products",
-  "invoices_issued",
-  "invoices_received",
-  "recurring_invoices"
-]New value: +[
+  "clients",
+  "products",
+  "invoices_issued",
+  "invoices_received",
+  "recurring_invoices",
+  "platform_sales",
+  "receipts"
+]
    • addedInput schema / properties / source
      Added value: +{
+  "description": "Platform / shop whose column layout the template should use",
+  "enum": [
+    "uber",
+    "bolt",
+    "glovo",
+    "tazz",
+    "woocommerce",
+    "prestashop"
+  ],
+  "type": "string"
+}
  2. First observedv1.0.17

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description is consistent with that. It adds real context the annotations cannot: the response is base64-encoded CSV containing headers plus example rows, not a file or a URL. It does not mention size limits or company scoping, but the core behavior is disclosed.

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?

Three sentences, front-loaded with the action, then the return shape, then the optional-parameter nuance. No filler and nothing that repeats the schema verbatim.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the burden of describing the return value and does so precisely (base64 CSV with headers and example rows), and it connects to the downstream import_upload step. Nothing an agent needs to invoke this correctly is missing.

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 coverage is 100%, so the baseline is 3; the description beats it by explaining that `source` swaps the column layout to a named platform's export format rather than just naming the enum. `importType` and `companyId` are not elaborated beyond the schema, which is acceptable since their descriptions are complete.

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 and resource (download a CSV import template), names the required discriminator (importType), and contrasts the two modes (generic vs. platform/shop-specific columns). An agent can distinguish this from import_upload, import_preview, or import_sources without opening any 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?

Makes the workflow position explicit — fill in the returned template and send it via import_upload — and explains when to pass `source` (to get a platform's export layout instead of generic columns). It stops short of naming a when-not or pointing at import_sources for discovering valid platform values.

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