Skip to main content
Glama

Produkt anlegen

create_product
Idempotent

Save a new product or service of the connected facturo account, e.g. 'leg das als Produkt an'. name, price and unit are required; ask for what is missing. A product with the same name is returned instead of duplicated; change that one with update_product. The product then shows in list_products and at facturo.at.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "price": "<price>",
      "unit": "<unit>"
    },
    "name": "create_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName as it goes onto the invoice line, one line, e.g. 'Regiestunde' or 'Fliesen verlegen'
unitYesUnit the price is for, e.g. 'Std', 'Stk', 'm²', 'pauschal'
priceYesUnit price in EUR as it goes onto the invoice line, e.g. '95', '95.50' or '95,50'
vat_rateNoOptional own VAT rate in percent ('10', '13', '4,9'), only on accounts with per-line VAT rates. Empty string: the product follows the document's rate.
descriptionNoOptional standard specs (dimensions, scope, options). They prefill the item details whenever the product goes onto a line.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=false and idempotentHint=true, and the description makes that idempotency concrete: a same-named product is returned rather than duplicated. It also discloses the downstream effect (visible in list_products and at facturo.at). It stops short of stating permission/account requirements or what the returned object looks like.

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?

One compact paragraph, front-loaded with the action and its scope, then requirements, then the duplicate branch. Nothing is padded, though the 'facturo.at' visibility remark is the softest sentence.

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?

With no output schema and a fully documented input schema, the description covers the remaining gaps an agent needs: required fields, user phrasings, duplicate handling, and where the created product surfaces. The one gap is that it never states what the call returns or whether it consumes any quota.

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 baseline is 3; the description earns a bump by singling out name, price and unit as mandatory and instructing the agent to ask for whatever is missing, which tells it how to behave with partially-specified requests. It adds no format or syntax detail beyond the schema, which is fine because the schema already carries that.

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 opens with a specific verb and resource ('Save a new product or service of the connected facturo account') and anchors it to the user phrasing 'leg das als Produkt an'. It is immediately separable from siblings like update_product and list_products, which are named by role.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit trigger phrase, tells the agent to elicit the three required fields when absent, and redirects to update_product when a duplicate name is returned. That is a complete when-to-use and when-to-switch-elsewhere instruction set.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources