Skip to main content
Glama
Sign In
Storno CLI

Storno CLI

Official
by stornoro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

suppliers_create

Create a new supplier manually by providing name, registration number, address, city, and county; if a supplier with the same CIF already exists, return that existing record 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

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

A4/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive write, so the description does not need to restate that. It adds a meaningful behavioral trait beyond the annotations: a CIF-based dedupe that returns the existing supplier instead of creating a duplicate.

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 short sentences, front-loaded with the action, then the required fields, then the dedupe edge case. No sentence is wasted and the ordering supports quick scanning.

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 a 17-parameter mutation tool with rich schema descriptions and safety annotations, the description covers purpose, required inputs, and a key edge case. However, with no output schema it does not describe the normal success return value, which would be useful for an agent to know.

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 description coverage is 100%, so every parameter is documented in the schema. The description repeats the required fields but adds no format details, defaults, or meaning beyond what the schema already provides, so the baseline 3 applies.

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 ('Create a new supplier') and adds a scope modifier ('manually') that implicitly distinguishes it from bulk import or registry-sync siblings. An agent can identify this as the single-record creation tool without opening the schema.

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?

The word 'manually' hints that this is for hand-entered suppliers rather than imports, but no alternative tool is named and there is no explicit when-to-use or when-not-to-use guidance. The context is implied rather than stated.

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