Skip to main content
Glama

add_issue_note

Add a public or private comment to a MantisBT issue and optionally record time spent, keeping discussions and work logs attached to the correct ticket.

Instructions

Adds a note/comment to an issue in MantisBT, with visibility support (public/private) and time tracking.

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": {
      "issue_id": "<issue_id>",
      "text": "<text>"
    },
    "name": "add_issue_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesNote/comment text.
issue_idYes
view_stateNopublic
time_tracking_durationNoTempo gasto no formato HH:MM (ex: '01:30').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/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 burden for a write operation. It does not state that the note is attributed to the authenticated user, whether it is later editable/deletable via delete_issue_note, permission requirements, or what happens on failure. The public/private and time-tracking mentions largely restate what the schema already declares.

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 a clear verb-resource opening and no filler. The parenthetical feature list is compact, though it occupies space that could have carried mutation behavior instead.

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 with no annotations and no output schema, the definition is thin: it omits return shape, permission/auth expectations, and any side effects. An agent knows what the tool broadly does but not enough to invoke it confidently in edge cases.

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 50%: issue_id has no description and view_state is only self-documenting via its enum/default. The description names visibility and time tracking, mapping to two of four parameters, but adds no syntax or format detail beyond what the schema already provides (including the HH:MM format documented in the schema).

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 opens with a specific verb and resource ('Adds a note/comment to an issue in MantisBT'), which is clearly distinct from siblings such as add_issue_attachment, add_issue_relationship, and delete_issue_note. It does not explicitly name any sibling, but the resource is unambiguous enough that an agent can select it without opening the schema.

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 prerequisites, and no mention of alternatives (e.g., update_issue for edits vs. adding a comment). The only usage-adjacent content is a list of features, which describes capability rather than conditions for invocation.

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