Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

addresses_update

Updates a Macola address record using supplied field values so customer, contact, shipping, and tax details stay current. Accepts PUT or PATCH interchangeably for address maintenance.

Instructions

Updates the specified Address with the data provided. PUT and PATCH are interchangeable.

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": "addresses_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
IDNo
FaxNo
CityNo
MainNo
NotesNo
PhoneNo
CountyNo
AccountNo
ContactNo
FOBCodeNo
ShipViaNo
TaxableNo
UPSZoneNo
DivisionNo
PoNumberNo
PostCodeNo
TaxCode1No
TaxCode2No
TaxCode3No
StateCodeNo
RowVersionNo
AddressCodeNo
AddressTypeNo
CountryCodeNo
InvoiceTypeNo
SalesPersonNo
TaxScheduleNo
AddressLine1No
AddressLine2No
AddressLine3No
WarehouseCodeNo
InvoiceFrequencyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It says only that data is provided and that PUT/PATCH are interchangeable, without disclosing whether omitted fields are cleared or preserved, whether RowVersion is needed for concurrency, what permissions are required, or what the operation returns.

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 two short sentences and front-loads the operation. The second sentence is low-value and potentially confusing because PUT and PATCH have different replacement semantics, but the overall text is not bloated.

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

Completeness1/5

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

For a 32-parameter mutation with no annotations and no output schema, the definition is far too thin. It omits required fields, update semantics, concurrency handling, permissions, and return behavior, leaving the agent without essential context for invoking it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 32 parameters with 0% description coverage and no required fields. The description adds no meaning about which identifier field is used, what individual fields represent, or which fields are required, so it does not compensate for the schema's complete lack of parameter documentation.

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 the specific verb 'Updates' and resource 'Address', making the mutation intent clear against siblings such as addresses_create, addresses_get, and addresses_delete. It does not clarify how the target address is identified (ID vs AddressCode), but the core purpose is understandable.

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?

There is no when-to-use guidance, no prerequisites, and no alternative mentioned. The statement that 'PUT and PATCH are interchangeable' is a protocol remark, not guidance on choosing this tool over addresses_create or on partial versus full updates.

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