Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

comment_codes_create

Creates a new Comment Code (Shipping Instruction) in Macola 10 to define reusable shipping instructions for business records.

Instructions

Creates a new Comment Code (Shipping Instruction).

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

Input Schema

NameRequiredDescriptionDefault
RowVersionNo
CommentCodeNo
DescriptionNo
Description2No

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.6/5.0
Behavior2/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. It confirms a create/mutation but is silent on permission requirements, duplicate handling, default values for the optional fields, and what the call returns.

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

Conciseness3/5

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

A single front-loaded sentence with no filler, but its brevity is under-specification rather than tightness — the parenthetical is the only added information an agent could not have guessed.

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?

For a four-parameter mutation tool with no annotations, no output schema, and zero schema descriptions, the definition leaves too much unstated: field meanings, duplicate behavior, and return shape all require trial and error.

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

Parameters2/5

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

Schema description coverage is 0% across four parameters (RowVersion, CommentCode, Description, Description2). The description only hints that 'CommentCode' is the code being created; it says nothing about RowVersion, the purpose of a second description field, or which fields are effectively needed.

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?

States a specific verb plus resource: creates a new Comment Code, glossed as a Shipping Instruction. An agent can distinguish it from comment_codes_get/find/update/delete by the verb alone, though the description never explicitly contrasts them.

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 when-to-use, when-not-to-use, or prerequisite guidance. It does not say whether a code must be unique, whether the parenthetical 'Shipping Instruction' means this is a shipping-only resource, or which sibling to use to check for an existing code 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