Skip to main content
Glama

update_issue

Modify any field of an existing MantisBT issue—status, assignee, priority, severity, resolution, text, versions, tags, or custom fields—by specifying its issue ID.

Instructions

Updates any field of an existing MantisBT issue (status, assignee/handler, priority, severity, resolution, texts, versions, tags or custom fields).

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>"
    },
    "name": "update_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
summaryNo
issue_idYes
handler_idNoID of the new assignee.
descriptionNo
status_nameNo
category_nameNo
custom_fieldsNo
priority_nameNo
severity_nameNo
target_versionNo
resolution_nameNo
fixed_in_versionNo
steps_to_reproduceNo
additional_informationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations at all, the description carries the full burden of behavioral disclosure and does not meet it. It never says whether this is a partial/merge update or a replacement, whether changing status/resolution triggers notifications or workflow rules, whether changes are reversible, or what the response contains. For a wide multi-field mutation on an issue tracker, these are consequential gaps.

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?

A single front-loaded sentence that states the operation first and then the covered fields, with no filler or repetition. The parenthesis list is dense but every item carries information about scope.

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?

Fourteen parameters with near-zero schema documentation and no output schema or annotations mean the description should be doing much more work than one field list. It covers the surface area of the parameters but omits update semantics, enum meanings, and the custom_fields nesting, and it claims a tag capability the schema does not have.

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 description coverage is only 7% (just handler_id), so the description has to compensate, and it does partially by grouping fields into status, handler, priority, severity, resolution, texts, versions and custom fields. However, it adds no meaning about the enum values, the custom_fields array structure (field_id/value pairs), or which texts map to which parameters, and it references tags the schema does not support.

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?

Names a specific verb (updates) and resource (existing MantisBT issue) and enumerates the field families it can change, which lets an agent distinguish it from create_issue or delete_issue. It does not explicitly name a sibling or contrast with one, and it lists 'tags' even though the schema exposes no tag parameter, slightly muddying the field inventory.

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?

The word 'existing' implies the issue must already be present via issue_id, but there is no statement about when to use this versus create_issue or add_issue_note, no prerequisites such as required permissions, and no note about whether omitted fields are left untouched or reset. An agent gets the job of the tool but not the conditions that select it.

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