Skip to main content
Glama
stornoro

Storno CLI

by stornoro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

suppliers_create

Creates a new supplier using required fields such as name, address, county, and registration number. If the CIF already exists, returns the existing supplier instead.

Instructions

Create a new supplier manually. Requires name, county, city, address, and registration number. If a supplier with the same CIF already exists, returns the existing supplier instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cifNoTax identification number (CIF)
cityYesCity
nameYesSupplier name
emailNoEmail address
notesNoInternal notes
phoneNoPhone number
countyYesCounty
addressYesStreet address
countryNoCountry code ISO 3166-1 alpha-2 (default: RO)
vatCodeNoVAT code (e.g., RO12345678)
bankNameNoBank name
companyIdNoCompany UUID (overrides configured default)
affiliatedNoAffiliated party — D394 sets prsAfiliat = 1 when an affiliated partner appears on an invoice of the period
isVatPayerNoWhether supplier is a VAT payer (default: false)
postalCodeNoPostal code
bankAccountNoBank account (IBAN)
registrationNumberYesTrade registry number (e.g., J40/123/2020)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.48
    • addedInput schema / properties / affiliated
      Added value: +{
+  "description": "Affiliated party — D394 sets prsAfiliat = 1 when an affiliated partner appears on an invoice of the period",
+  "type": "boolean"
+}
  2. First observedv1.0.17

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are present, so the description must carry the burden. It discloses a non-obvious behavior—returning an existing supplier when CIF matches—and states required inputs. However, it doesn't disclose return value shape, validation/error behavior, or whether CIF is required for dedup to trigger.

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 action and required fields, followed by the dedup rule. No filler or repetition of schema text.

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

Completeness3/5

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

For a 17-parameter mutation with no annotations and no output schema, the description omits the return value and error semantics and leaves the role of optional CIF vs required registrationNumber slightly ambiguous. Schema covers parameters, so it's usable, but not fully complete.

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?

All 17 parameters have schema descriptions (100% coverage), so baseline is 3. The description adds cross-parameter meaning by identifying CIF as the duplicate-key for the upsert behavior and consolidating the required field set.

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+resource ('Create a new supplier manually'), lists the five required fields, and notes the dedup fallback. This clearly distinguishes it from supplier get/list/update/delete siblings.

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?

Gives context that this is for manual supplier creation and enumerates prerequisites, but does not name alternatives or when not to use it (e.g., bulk import or ANAF sync), leaving the choice partly implied.

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