Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

comment_codes_get

Retrieve a comment code by its ID to identify or reference the comment associated with a specific entry.

Instructions

Get the Comment Code for a particular entry by specifying its ID.

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

Input Schema

NameRequiredDescriptionDefault
idYesComment code ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/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 disclosure burden. It implies a read-only single-record fetch, but says nothing about behavior on a missing/invalid ID, whether the response is a single object or empty, or any access constraints — gaps that matter for a tool with no structured safety hints.

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 front-loaded sentence with no filler; the verb and resource lead. Slightly loose wording ("particular entry" is vaguer than "comment code record") keeps it from being a 5.

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 lookup with full schema coverage and no output schema, little is strictly required, and the description covers the core operation. It is still thin on not-found behavior and on what the returned comment code contains, which an agent may need to decide whether to call it.

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?

There is one parameter with 100% schema description coverage ("Comment code ID"), so the schema already documents it fully and the baseline is 3. The phrase "specifying its ID" merely restates the schema and adds no format, source, or validation detail.

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?

The description states a specific verb and resource ("Get the Comment Code") plus the retrieval key ("by specifying its ID"), which is enough to distinguish it from mutation siblings like comment_codes_create/delete/update. It stops short of naming comment_codes_find as the lookup-by-search alternative, so the distinction is only implied.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"By specifying its ID" implies the precondition that the caller already holds an ID, which is useful usage context. However, it gives no explicit when-to-use guidance versus comment_codes_find for callers who don't know the ID, and no statement about what to do when the ID is invalid.

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