Skip to main content
Glama
stornoro

Storno CLI

by stornoro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

import_template

Get a CSV template for any supported import type (clients, products, invoices, receipts). Choose a platform source like Uber, Glovo, or WooCommerce to match its specific column layout, then fill and upload via the import tool.

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

TableJSON 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.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses the return format (base64-encoded CSV) and content specifics, which is valuable. However, it doesn't mention potential errors (e.g., what happens for invalid importType/source combinations) or any authentication requirements.

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?

Two sentences with a clear front-loaded description of the tool's action and output. The second sentence adds context about platform templates. It's appropriately sized, though it could be slightly tightened without losing information.

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 there is no output schema, the description does a good job explaining the return value (base64 CSV with headers/example rows). The tool is relatively simple with only one required parameter. It lacks some edge-case behavior notes but is otherwise adequate 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.

Parameters4/5

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

Schema coverage is 100%, so the schema already documents all three parameters with descriptions. The description adds value by explaining the distinction between generic templates and source-specific ones, which clarifies the semantic of the 'source' parameter beyond its enum listing.

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 clearly states the tool downloads a CSV template, specifies the format as base64-encoded CSV with column headers and example rows, and distinguishes between generic templates and platform-specific ones (uber, bolt, glovo, etc). The verb-resource pairing is concrete and specific.

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?

The description explicitly tells the agent when to use this tool (downloading a CSV template before filling and uploading via import_upload) and explains the alternative of passing a source for platform/shop-specific templates. It lacks an explicit 'don't use when...' statement, but the purpose is clear and the synergy with import_upload is well articulated.

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