Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

addresses_create

Creates a new address record in Macola 10 with details such as address lines, city, postal code, country, contact, tax codes, and shipping info, for use in customer and order data.

Instructions

Creates a new Address.

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_create"
  }
}

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

D1.5/5.0
Behavior1/5

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

With no annotations supplied, the description carries the full behavioral burden and discloses essentially nothing: not whether the operation is idempotent, what permissions or auth are needed, which fields must be present (schema says zero required), what happens on duplicate codes, or whether the created record is returned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is short but the brevity is under-specification rather than efficiency; it wastes no words yet conveys no information beyond the title. Nothing is front-loaded because there is nothing to front-load.

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 tool with no annotations and no output schema, the definition is drastically incomplete. An agent cannot determine required inputs, validation rules, the response shape, or error behavior from this description.

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 schema exposes 32 parameters with 0% description coverage, including ambiguous names like 'Main', 'Taxable', 'Division', 'InvoiceType', 'RowVersion', and 'AddressType'. The description provides no meaning for any of them, so an agent must guess at field semantics and value formats.

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

Purpose2/5

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

The description restates the tool name almost verbatim: 'Creates a new Address' adds nothing an agent could not infer from 'addresses_create'. It names a verb and resource, but no scope, no distinction from addresses_update or addresses_address_book, and no indication of what an Address entity comprises.

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 (e.g. required identifiers, uniqueness of AddressCode), and no reference to alternatives such as addresses_update or addresses_find. The only implicit signal is that a create operation is for new records.

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