Skip to main content
Glama

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

NameRequiredDescriptionDefault
auto_syncNoIf true (or if the vector store is empty), syncs issues from the MantisBT API before analyzing.
handler_idNoFilter the analysis by a specific assignee.
project_idNoFilter the analysis by a specific project.
max_sync_pagesNo
stale_threshold_hoursNoHours without update after which an open issue is considered stagnant (default 168h = 7 days).
cluster_similarity_thresholdNoCosine similarity threshold (0.1 to 0.95) for grouping recurring issues into semantic clusters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does add real context about the data source (MantisBT issue vector store) and the computed outputs. However, it does not disclose that the tool can mutate state by syncing issues from the MantisBT API into the vector store, does not state that it is otherwise read-only, and gives no sense of cost/latency for an analysis that computes clustering and percentiles. Those gaps are material for an unannotated tool.

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?

It is a single dense sentence that front-loads the purpose and then lists outputs, with essentially no filler. The long enumeration is harder to scan than a short structured list, but every clause carries information about what is returned.

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?

There is no output schema, so the description must convey return content, and it does so by enumerating every computed metric plus the 0-100 Efficiency Score and diagnostics. It stops short of describing the response structure (field names, nesting of per-developer or cluster results) and of covering the sync side effect, which keeps it from a 5 for a tool of this complexity.

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 83%, so the schema already documents nearly every parameter, making 3 the baseline. The description adds marginal linkage by naming outputs that correspond to inputs ('stagnant/overdue issues' for stale_threshold_hours, 'semantic clusters' for cluster_similarity_threshold) but does not explain filtering semantics like handler_id or project_id scope beyond what the schema states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb ('Analyzes') and a precise resource ('project engineering efficiency') and then enumerates the exact metrics produced: resolution rate, mean/P50/P90 lead time, rework rate, ping-pong, stagnant issues, per-developer efficiency, semantic clusters, and an Efficiency Score. No sibling tool in the list performs efficiency analytics, so an agent can immediately distinguish this from sync_issues_to_vector_store or search_vector_issues.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the agent can infer this is the analytics entry point over the MantisBT vector store. There is no explicit when-to-use versus when-not-to-use statement, no indication of how it relates to search_vector_issues or sync_issues_to_vector_store, and no prerequisites (e.g., that it may need to populate the vector store first, which the schema's auto_sync hints at).

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