Skip to main content
Glama

list_issues

Retrieve and filter MantisBT issues by project, saved filter, assignee, reporter, status, or text search to find relevant bugs and track work.

Instructions

Lists and filters MantisBT issues by project, saved filter, assignee (handler), reporter, status or text search.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_issues"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
filter_idNoID of a saved filter, or 'assigned', 'reported', 'monitored', 'unassigned'.
page_sizeNo
handler_idNoIn-memory filter by assignee ID.
project_idNo
search_textNoCase-insensitive search in summary, description and notes.
only_unresolvedNoIf true, returns only issues with status < 80.

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 entire behavioral burden and discloses very little: it does not say the operation is read-only, how results are ordered, whether pagination is required, or that results are capped by page_size. The only behavioral signal is the bare word 'lists'.

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 no filler; the filter dimensions are enumerated compactly. It could have spent the same words on load-bearing details instead of filters that do not exist in the schema.

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?

For a 7-parameter read tool with no annotations and no output schema, the description is thin: it omits pagination behavior, default ordering, and the return shape. An agent could still call it correctly because the schema carries defaults, but it would be guessing about result size and ordering.

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 57%, and the description does add real value by mapping 'assignee' to the schema's handler_id, which resolves a vocabulary mismatch an agent could easily get wrong. However, it never explains page/page_size, only_unresolved, or the filter_id special values ('assigned', 'reported', 'monitored', 'unassigned'), and it names 'reporter' and 'status' filters that have no corresponding parameters.

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?

States a specific verb ('Lists and filters') and resource ('MantisBT issues'), then enumerates the filter dimensions, which is enough for an agent to recognize it as the general issue-listing tool. It does not differentiate itself from siblings such as search_vector_issues or get_my_unresolved_assigned_context, so it stops short of a 5.

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 or when-not-to-use guidance and no mention of alternatives, despite siblings that overlap heavily (search_vector_issues, get_my_unresolved_assigned_context, list_filters). The agent must infer from the name alone that this is the plain-vs-semantic listing path.

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