Skip to main content
Glama

create_issue

Creates a new MantisBT issue with summary, project, description, priority, severity, assignment, tags, and custom fields; use it to log bugs or feature requests through the MCP server.

Instructions

Creates a new issue in MantisBT.

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": {
      "summary": "<summary>",
      "description": "<description>",
      "project_id": "<project_id>"
    },
    "name": "create_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNo
summaryYesIssue title/summary.
versionNo
handler_idNoID of the user to assign the issue to.
project_idYesProject ID.
descriptionYesDetailed issue description.
category_nameNoCategory name in the project (e.g. 'General', 'Bug').General
custom_fieldsNo
priority_nameNo
severity_nameNo
target_versionNo
steps_to_reproduceNo
additional_informationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2/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 behavioral burden, yet it discloses only that a mutation creates an issue. It says nothing about required permissions, whether notifications or emails are triggered, what defaults apply (category 'General', priority, severity), or whether the created issue is returned.

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

Conciseness3/5

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

The single sentence is front-loaded and free of waste, but its brevity reflects under-specification rather than efficient communication. There is no structure to guide an agent through a 13-parameter creation call.

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 mutation tool with 13 parameters, no annotations, and no output schema, a one-sentence restatement is far from sufficient. An agent gets no information about required preconditions, defaults, side effects, or what a successful call returns.

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

Parameters2/5

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

Schema description coverage is only 38% across 13 parameters, so the description is expected to compensate, and it provides no parameter information whatsoever. The only mitigation is that the three required fields (summary, description, project_id) happen to be described in the schema itself; everything else, including the two enums and custom_fields, is left to the schema alone.

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 text 'Creates a new issue in MantisBT' restates the tool name (create_issue) plus the product name and adds no scope, object model, or distinguishing detail. Nothing separates it from siblings such as add_issue_note or add_issue_relationship beyond the bare verb.

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 (e.g. a valid project_id must already exist), and no mention of alternatives like add_issue_note for comment-only additions or update_issue for edits. The agent must infer everything from the name.

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