Skip to main content
Glama
dpesch

MantisBT MCP Server

by dpesch
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Add Note to Issue

add_note

Add a comment to an existing MantisBT issue with optional public or private visibility, returning the created note's details and direct link.

Instructions

Add a note (comment) to an existing MantisBT issue. Returns the created note object including id, created_at, reporter, text, view_state, and a view_url linking directly to the note in the MantisBT web UI.

Full UTF-8 text is supported. Markdown syntax is stored as-is — rendering depends on the MantisBT instance's configured text renderer.

Use view_state="private" to restrict the note to users with reporter-level access or higher; public notes are visible to all users who can view the issue.

Prerequisites: obtain issue_id from list_issues, get_issue, or search_issues.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesNote text (minimum 1 character). Full UTF-8 including emoji is supported. Markdown is stored as-is.
issue_idYesNumeric issue ID — use list_issues or get_issue to obtain issue IDs
view_stateNoVisibility of the note: "public" (visible to all, default) or "private" (visible only to users with sufficient access level).public

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Addedv1.10.4
  2. Removed
  3. Changed3 schema fields changedv1.10.3
    • changedInput schema / properties / issue_id / description
      Previous value: -"Numeric issue ID"New value: +"Numeric issue ID — use list_issues or get_issue to obtain issue IDs"
    • changedInput schema / properties / text / description
      Previous value: -"Note text (supports full UTF-8, markdown will be stored as-is)"New value: +"Note text (minimum 1 character). Full UTF-8 including emoji is supported. Markdown is stored as-is."
    • changedInput schema / properties / view_state / description
      Previous value: -"Visibility of the note (default: public)"New value: +"Visibility of the note: \"public\" (visible to all, default) or \"private\" (visible only to users with sufficient access level)."
  4. First observedv1.5.6

TDQS

A4.7/5.0
Behavior5/5

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

Goes beyond minimal annotations: describes return object, UTF-8 support, Markdown handling dependency on config, and view_state access levels. No contradictions with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Five well-organized sentences with no redundancy. Front-loaded with purpose and return, then details, then prerequisites.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Complete coverage for a tool with 3 parameters and no output schema: describes return fields, encoding, behavior, and prerequisites. No gaps.

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?

Schema coverage is 100%; description adds practical context for each parameter, such as details on encoding for text and how to obtain issue_id. Adds value beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the action 'Add a note (comment) to an existing MantisBT issue' and specifies the return object with fields. Distinguishes from sibling tools like delete_note and list_notes.

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

Usage Guidelines4/5

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

Provides prerequisites for obtaining issue_id and explains when to use private vs public view_state. Lacks explicit guidance on when not to use this tool or alternatives, but context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dpesch/mantisbt-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server