Skip to main content
Glama

Add count comment

add_count_comment

Write a comment on a count. body is 1 to 4000 characters. Optional list_id (a batch of this count), item_id, and barcode say what the comment is about. Returns the comment. The comment is saved under the user who owns this key. Requires the stock plan feature.

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": {
      "count_id": "<count_id>",
      "body": "<body>"
    },
    "name": "add_count_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
barcodeNo
item_idNo
list_idNo
count_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already establish that this mutates state (readOnlyHint=false, destructiveHint=false, non-idempotent). The description adds genuinely useful context beyond them: the return value, that the comment is attributed to the key's owning user, and a plan-level prerequisite. It does not state whether repeated calls create duplicate comments, whether the count must be open, or what happens on invalid count_id, which matters for a non-idempotent write.

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?

Four short sentences, front-loaded with the action, then target qualifiers, then return and prerequisite. The only wasted clause is the body length restatement already encoded in the schema constraints.

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?

No output schema exists, and the description at least signals "Returns the comment" rather than a bare status. However, for a non-idempotent write with five parameters and no annotation detail on side effects, an agent still lacks guidance on failure modes, duplicate behavior, and which parameter combinations are valid versus conflicting.

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

Parameters4/5

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

With 0% schema description coverage the description must carry the load, and it mostly does: list_id is explained as "a batch of this count", and item_id/barcode are grouped as target qualifiers. The body 1–4000 character note merely restates the schema's minLength/maxLength, and count_id, the primary required parameter, gets no explanation at all.

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?

"Write a comment on a count" gives a specific verb and resource, and the description distinguishes this from reading comments by noting it returns the created comment and ties it to a count, list, item, or barcode. It stops short of naming list_count_comments as the read-side sibling, so an agent must infer the pairing.

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?

Usage is only implied: the tool is obviously for adding commentary to a count, and a plan prerequisite is stated ("Requires the stock plan feature"). There is no explicit when-to-use or when-not-to-use guidance relative to siblings such as list_count_comments or update_count, leaving routing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources