Skip to main content
Glama
AIWerk

mcp-server-smallinvoice

by AIWerk

create_contact

Create a contact in smallinvoice by providing required details: relation, type, name, and main address.

Instructions

Creates new contact

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numberNounique number - default value: 'next free number'
relationYestype of contact's relation; possible values: CL - Customer, CR - Creditor
typeYestype of contact; possible values: C - Company, P - Private
genderNogender of contact (required for P type); possible values: M - Male, F - Female
gender_salutation_activeNowhether to show Mr./Ms. before contact name (for P type only) - default value: false
nameYesname of contact
name_additionNoadditional text for contact name
salutationNoe.g. Dear Mr. Jones
phoneNocontact phone number
faxNocontact fax number
emailNocontact email address
websiteNocontact website address
notesNoadditional notes
communication_languageNomain communication language - default value: 'default documents language'
communication_channelNopossible values: U - No preference, E - Documents by e-mail, P - Documents by post - default value: 'U'
communication_newsletterNopossible values: A - Send to main e-mail address and contacts, M - Only send to main e-mail address, N - No newsletter wanted - default value: 'A'
currencyNodefault currency
ebill_account_idNoe-bill account identification number
vat_identificationNoVAT identification number
vat_rateNodefault VAT rate
discount_rateNodefault discount rate - default value: 0
discount_typeNodefault discount type; possible valuesP - in %, A - Amount - default value: 'P'
payment_graceNodefault payment deadline
hourly_rateNocost per hour
custom_fieldsNocustom fields values
main_addressYesmain address of contact
Behavior2/5

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

Annotations indicate readOnlyHint=false and destructiveHint=false, which is consistent with a creation operation. However, the description adds no behavioral details beyond the obvious, such as the side effects of creating a contact, authentication requirements, or data integrity constraints. The openWorldHint=true is not explained.

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 a single sentence with no extraneous words. It is appropriately concise and front-loaded, conveying the core purpose immediately.

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

Completeness2/5

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

Given the tool's complexity (26 parameters, nested objects, multiple related sibling tools), the description is severely lacking. It does not explain what a contact is, how it relates to contact persons or addresses, or any prerequisites. The annotations provide minimal context, and the output schema is absent, leaving the AI with insufficient information to use the tool effectively.

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 the input schema already documents all 26 parameters thoroughly. The description does not add any additional meaning or context for the parameters, which is acceptable since the schema is complete, but it misses an opportunity to highlight important relationships (e.g., between type and gender).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Creates new contact' clearly states the verb (creates) and resource (contact). However, it does not distinguish this tool from sibling tools like create_contact_person, create_contact_address, and similar creation tools, which reduces clarity about when to use this specific tool.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. Sibling tools such as create_contact_person and create_contact_address exist, and the description offers no context about the relationship between contacts and sub-entities, making it hard for the AI to choose correctly.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AIWerk/mcp-server-smallinvoice'

If you have feedback or need assistance with the MCP directory API, please join our Discord server