get_my_unresolved_assigned_context
Collects all unresolved issues assigned to you or a specified user, including full descriptions, comments, custom fields, history, and a summary grouped by project, priority, and status.
Instructions
MAIN FUNCTION: Collects everything about all issues assigned to the user (or to a specific user) that are not yet resolved/closed. Returns the full description, steps to reproduce, additional information, complete notes/comments, custom fields, relationships, tags, attachment metadata, change history, and an executive summary grouped by project/priority/status to give the LLM full context.
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": "get_my_unresolved_assigned_context"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| filter_id | No | Saved filter ID in MantisBT or 'assigned' (default tries 'assigned' and falls back to a paginated scan). | |
| max_pages | No | Maximum number of pages (50 issues each) to scan during collection. | |
| project_id | No | Filter by a specific project ID. If omitted, searches all projects. | |
| include_history | No | Include the audit/transition history of each issue. | |
| assignee_user_id | No | ID of the assigned user. If omitted, automatically uses the authenticated user (/users/me). | |
| hydrate_individual_issues | No | If true, performs an individual GET /issues/{id} when the instance listing omits deep fields. | |
| resolved_status_threshold | No | Minimum status ID considered resolved in MantisBT (default 80 = resolved, 90 = closed). |