Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

contacts_create

Create a new contact record in Macola 10 with names, contact details, account links, and status fields to support customer and business data workflows.

Instructions

Creates a new Contact.

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

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

D1.5/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full behavioral burden for a mutation tool with 26 parameters, and it discloses nothing. It does not say whether any field is required, how duplicates are handled, what defaults apply to Active or isMain, or what the response contains.

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 contains no filler, but it is under-specified rather than concise. There is no structure to front-load because there is essentially no content beyond the tool name.

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 26-parameter create operation with no annotations and no output schema, the description is completely inadequate. An agent has no basis to decide which fields to populate or what a successful call returns.

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?

Schema description coverage is 0% across 26 parameters, and the description compensates for none of it. Fields like Active (number rather than boolean), isMain, Division, AccountManager, and RowVersion have no meaning conveyed anywhere.

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?

"Creates a new Contact" restates the tool name contacts_create with a verb and a resource, so the basic operation is inferable. It adds nothing about scope, required fields, or how it differs from contacts_update or contacts_find, making it a near-tautology.

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 mention of prerequisites (e.g. an existing Account), and no routing to alternatives such as contacts_update for existing records. The agent must infer usage entirely from the tool name.

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