Skip to main content
Glama
AIWerk

mcp-server-smallinvoice

by AIWerk

update_contact

Update existing contact details including name, email, phone, and address. Modify relation type, communication preferences, and custom fields.

Instructions

Updates specified contact

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contact_idYescontact ID
numberNounique number
relationNotype of contact's relation; possible values: CL - Customer, CR - Creditor
typeNotype 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)
nameNoname 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
communication_channelNopossible values: U - No preference, E - Documents by e-mail, P - Documents by post
communication_newsletterNopossible values: A - Send to main e-mail address and contacts, M - Only send to main e-mail address, N - No newsletter wanted
currencyNodefault currency
ebill_account_idNoe-bill account identification number
vat_identificationNoVAT identification number
vat_rateNodefault VAT rate
discount_rateNodefault discount rate
discount_typeNodefault discount type; possible valuesP - in %, A - Amount
payment_graceNodefault payment deadline
hourly_rateNocost per hour
custom_fieldsNocustom fields values
Behavior2/5

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

The description adds no behavioral context beyond the annotations. Annotations indicate it is not read-only and not destructive, but the description does not disclose side effects, permissions, or partial update behavior. For a mutation tool with many parameters, more transparency is expected.

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?

The description is very concise at one sentence. While it could benefit from a bit more detail, it is not verbose and follows a simple structure.

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, no output schema), the description is too minimal. It does not explain return values, success/error conditions, or constraints like partial update support. More context is needed for effective use.

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?

The input schema provides full coverage (100%) with descriptions for all 26 parameters. The description does not add additional meaning or clarify parameter interactions, so the baseline score of 3 is appropriate.

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 clearly states the action ('Updates') and the resource ('specified contact'). It is a specific verb and resource but does not differentiate from sibling tools like update_contact_person or update_contact_address, which update related entities rather than the main contact record.

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 such as get_contact (for reading), create_contact (for creating), or update_contact_person (for updating a specific person within the contact). The description lacks context for appropriate use.

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