Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

comment_codes_delete

Deletes a specified Comment Code (Shipping Instruction) by ID, removing obsolete shipping instructions from Macola data.

Instructions

Deletes the specific Comment Code (Shipping Instruction).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
idYesComment code ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It says the operation deletes, but does not state whether deletion is permanent or reversible, what permission or authorization levels are required, what happens to records referencing the comment code, or what the response contains on success/failure.

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?

A single short sentence with the verb front-loaded and no redundant clauses. The word "specific" is filler and could be dropped, but overall the statement is efficient.

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 one-parameter delete tool with no output schema, the description covers identity and action, which is the minimum an agent needs to invoke it. However, with zero annotations and no destructive-behavior disclosure, it omits the caveats that matter most for an irreversible operation.

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 coverage is 100% and the single `id` parameter is documented as "Comment code ID to delete", so the description adds nothing beyond the schema. With one fully documented parameter, the baseline of 3 applies.

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 ("Deletes") and resource ("Comment Code"), and the parenthetical "(Shipping Instruction)" clarifies the domain meaning of the resource. The delete-vs-create/find/get/update distinction is obvious from the name/verb without needing sibling descriptions.

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 guidance on when to delete versus updating a comment code, no prerequisites (e.g. whether the code must be unreferenced before deletion), and no note about confirming destructive intent. The agent must infer everything about selection.

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