analyze_project_efficiency
Analyzes MantisBT project issues to compute resolution rates, lead times, rework, stagnant items, developer efficiency, recurring bottlenecks, and a 0–100 Efficiency Score with diagnostics.
Instructions
Analyzes project engineering efficiency via the MantisBT issue vector store: computes resolution rate, mean/P50/P90 lead time, rework rate (reopens), assignee ping-pong, stagnant/overdue issues, efficiency per developer, semantic clusters of recurring bottlenecks, and an Efficiency Score (0-100) with actionable diagnostics.
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": "analyze_project_efficiency"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| auto_sync | No | If true (or if the vector store is empty), syncs issues from the MantisBT API before analyzing. | |
| handler_id | No | Filter the analysis by a specific assignee. | |
| project_id | No | Filter the analysis by a specific project. | |
| max_sync_pages | No | ||
| stale_threshold_hours | No | Hours without update after which an open issue is considered stagnant (default 168h = 7 days). | |
| cluster_similarity_threshold | No | Cosine similarity threshold (0.1 to 0.95) for grouping recurring issues into semantic clusters. |