Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

comment_codes_find

Find Comment Codes (Shipping Instructions) in Macola 10 by division, historic status, or code, with paging, field selection, distinct values, and count options.

Instructions

Find some or all Comment Codes (Shipping Instructions).

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

Input Schema

NameRequiredDescriptionDefault
pageNo
skipNo
fieldsNo
distinctNo
divisionNo
historicNo
pageSizeNo
countOnlyNo
totalCountNo
CommentCodeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

D1.8/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 burden of behavioral disclosure, yet it says nothing about pagination, default filtering, permissions, or what is returned. It only implies a read-style lookup by using 'Find'.

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 under-specified rather than concise. It has no structure that helps an agent understand scope, filtering, or pagination.

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 10-parameter finder with no annotations, no output schema, and no parameter documentation, the description is far too thin. An agent cannot determine how to invoke it correctly or interpret the result.

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% and the description explains none of the 10 parameters. Terms like page, skip, fields, distinct, historic, countOnly, totalCount, division, and CommentCode are left entirely undefined in both schema and description.

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 essentially restates the tool name: 'Find ... Comment Codes' adds only the parenthetical 'Shipping Instructions'. It does not distinguish this finder from the sibling comment_codes_get or clarify whether it is a bulk/list operation.

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 when to choose comment_codes_get instead, and no prerequisites. The phrase 'some or all' hints at a list capability but gives no conditions for selecting it.

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