Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

contacts_update

Update an existing Macola contact by ID or ContactID, changing only the fields supplied and returning before-and-after values.

Instructions

Updates a Contact. Identify it by ID (the number, e.g. 7029) or ContactID (the GUID); the tool looks up the contact, its current RowVersion and stored email itself, so pass only the fields you want to change (e.g. { ID: 7029, Email: "new@example.com" }). Returns the changed fields before and after.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "contacts_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
IDNo
FaxNo
EmailNo
PhoneNo
TitleNo
ActiveNo
GenderNo
MobileNo
isMainNo
AccountNo
EndDateNo
DivisionNo
FullNameNo
InitialsNo
JobTitleNo
LanguageNo
LastNameNo
ContactIDNo
ExtensionNo
FirstNameNo
StartDateNo
MiddleNameNo
RowVersionNo
ContactNoteNo
AccountManagerNo
JobDescriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses implicit server-side lookup of the contact, its RowVersion and stored email (so the caller need not read-then-write), that it is a partial/merge update, and that it returns before-and-after values for changed fields. It stops short of stating permission requirements, validation failure behavior, or reversibility.

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?

Three compact sentences, front-loaded with the core action, and the inline example payload earns its space by showing partial-update shape. The first sentence is a dense semicolon chain, but nothing is redundant.

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

Completeness3/5

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

For a 26-parameter mutation with no annotations, no output schema and zero schema descriptions, the definition covers the essential call mechanics and return shape well. It remains incomplete on field-level meaning and value formats for the majority of the 26 optional attributes, which an agent would still have to guess at.

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 0% across 26 parameters, so the description must compensate. It explains the two key parameters (ID vs. ContactID), that RowVersion is resolved internally, and that unspecified fields are left untouched — a meaningful reduction of the 26-field surface — but it gives no formats for dates (StartDate/EndDate), no encoding for Active or Division, and no hint about what Account or AccountManager expect.

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 states a specific verb and resource ('Updates a Contact') and clarifies the two identifier paths (numeric ID vs. GUID ContactID). It is unambiguous about what the tool does, though it never names a sibling such as contacts_create or contacts_get to delimit it.

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 genuinely actionable usage context: identify the record by ID or ContactID, and pass only the fields to change because the tool resolves RowVersion and stored email itself. Missing is any explicit when-not guidance (e.g., use contacts_create for new records, contacts_find to locate an ID first).

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