Skip to main content
Glama
Storno CLI

Storno CLI

Official
by stornoro

clients_create

Creates a new company or individual client record manually; supports auto-filling company details via ANAF lookup or registry before saving.

Instructions

Create a new client manually. Supports both company and individual client types. Company details (address, VAT, bank account, etc.) can be auto-filled using clients_anaf_lookup or clients_from_registry before calling this tool.

Input Schema

NameRequiredDescriptionDefault
cnpNoPersonal numeric code / CNP (for individual type)
cuiNoCompany tax ID / CUI (for company type)
cityNoCity
nameYesClient name (company or individual full name)
typeNoClient type: "company" (default) or "individual"
emailNoClient email address
notesNoInternal notes about the client
phoneNoClient phone number
countyNoCounty / state
statusNoPartner rule: active (default), warning (a notice is shown when the client is picked on an invoice) or blocked (the client cannot be invoiced — issue is refused)
addressNoStreet address
countryNoISO 3166-1 alpha-2 country code (default: RO)
vatCodeNoVAT registration code (e.g., RO12345678)
bankNameNoBank name
currencyNoPreferred currency for this client (ISO 4217, e.g., EUR, USD, RON)
idNumberNoClient identification number (personal ID, passport, etc.)
companyIdNoCompany UUID override (uses active company if not set)
affiliatedNoAffiliated party — D394 sets prsAfiliat = 1 when an affiliated partner appears on an invoice of the period
isVatPayerNoWhether the client is registered for VAT
postalCodeNoPostal / ZIP code
bankAccountNoIBAN or bank account number
creditLimitNoPartner rule: maximum outstanding balance in the company currency; issuing an invoice that would exceed it returns a `warning` (never a refusal). null removes the limit
contactPersonNoName of the primary contact person
registrationNumberNoTrade registry number (e.g., J40/1234/2020)
defaultPaymentTermDaysNoDefault payment term in days for invoices issued to this client

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields 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"
      +}
    • addedInput schema / properties / creditLimit
      Added value: +{
      +  "anyOf": [
      +    {
      +      "minimum": 0,
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Partner rule: maximum outstanding balance in the company currency; issuing an invoice that would exceed it returns a `warning` (never a refusal). null removes the limit"
      +}
    • addedInput schema / properties / status
      Added value: +{
      +  "description": "Partner rule: active (default), warning (a notice is shown when the client is picked on an invoice) or blocked (the client cannot be invoiced — issue is refused)",
      +  "enum": [
      +    "active",
      +    "warning",
      +    "blocked"
      +  ],
      +  "type": "string"
      +}
  2. First observedv1.0.17

TDQS

A4/5.0
Behavior3/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, non-idempotent mutation, and the description's 'Create' matches that. The description adds useful workflow context about manual creation and data prefill, but it does not disclose duplicate handling, validation behavior, permission requirements, or side effects beyond what annotations and schema provide.

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 tight sentences with no filler. It is front-loaded with the core action and then provides the most relevant workflow detail: client type support and prefill alternatives.

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 the rich 100%-covered schema and present annotations, the description covers the essential purpose and prefill workflow for a complex create tool. It is slightly incomplete because it does not mention return behavior, duplicate-name handling, or other post-creation effects, and there is no output schema to cover those aspects.

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 all 25 parameters are already well documented in the input schema. The description only adds high-level context that company fields can be pre-filled via lookup tools and that both company and individual types are supported, which is helpful but does not add detailed parameter-level semantics beyond the schema.

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: create a new client manually. It also distinguishes supported client types and names the lookup tools used for auto-filling company details, so an agent can identify its role among siblings.

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 gives clear usage context: use this tool to create manually, and use clients_anaf_lookup or clients_from_registry beforehand to populate company details. It does not explicitly state when not to use it or mention bulk/import alternatives, so it stops short of a 5.

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