Skip to main content
Glama

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

NameRequiredDescriptionDefault
filter_idNoSaved filter ID in MantisBT or 'assigned' (default tries 'assigned' and falls back to a paginated scan).
max_pagesNoMaximum number of pages (50 issues each) to scan during collection.
project_idNoFilter by a specific project ID. If omitted, searches all projects.
include_historyNoInclude the audit/transition history of each issue.
assignee_user_idNoID of the assigned user. If omitted, automatically uses the authenticated user (/users/me).
hydrate_individual_issuesNoIf true, performs an individual GET /issues/{id} when the instance listing omits deep fields.
resolved_status_thresholdNoMinimum status ID considered resolved in MantisBT (default 80 = resolved, 90 = closed).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the breadth of what comes back (notes, history, relationships, attachment metadata, executive summary), which is real behavioral information, but it omits cost/volume implications of a deep multi-issue collection, pagination behavior (max_pages caps at 50 issues per page), and the fallback scan path described only in the schema.

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?

One dense, front-loaded sentence: the core scope comes first and the returned-field list follows. The 'MAIN FUNCTION:' prefix is mildly redundant and the enumeration is long, but since there is no output schema that enumeration earns its place.

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

Completeness4/5

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

With no output schema and seven documented parameters, the description correctly spends its words on return contents. The main remaining gap is routing guidance against the sibling issue-reading tools; everything needed to invoke it, including parameter semantics, lives in the schema.

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 100%, so the baseline is 3. The description only echoes the schema's semantics by saying 'the user (or a specific user)' and 'not yet resolved/closed'; it adds no extra nuance on filter_id, hydrate_individual_issues, or the resolved_status_threshold default (80/90 already stated in the schema).

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 ('Collects') and a precise resource scope: all unresolved issues assigned to the authenticated user or a named user, with an enumerated payload. It is distinguishable from single-issue siblings like get_issue_full_context, but it never names list_issues or get_issue_full_context to sharpen the boundary.

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 explicit when-to-use or when-not-to-use guidance and no alternatives are mentioned. An agent must infer from the name and the phrase 'to give the LLM full context' that this is a bulk context-gathering call rather than a targeted lookup.

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