Engineering-operations analytics MCP server providing tools for delivery flow, cost, signals, and people metrics across company, project, team, and person scopes.
Two tools with well-crafted descriptions (spend_summary: 189 chars, signals: 234 chars) that explain WHAT, WHEN, and WHY. Input schemas present with typed parameters and descriptions. However, output schemas are not documented in the source code provided, and parameter descriptions lack format constraints (e.g., date format validation, scope ID format). Tool names are clear action verbs (spend_summary, signals) but lack the verb_noun pattern (get_spend_summary, list_signals would be stronger). No evidence of error handling guidance or recovery paths in the definitions.
Open and recent signals (idle, bench, missing timesheets, review gaps, worklog-vs-git discrepancies…) for a scope and period. Use when asked what needs attention, what looks wrong, or anything about a specific signal. Read opmetrics://signals-model first: signals are indications with stated evidence, never verdicts.
Per-person spend (salary + AI + tooling) for a scope and period, with totals. Use when the question is about money, cost, payroll, AI spend or where resources go. Takes company, project or team scope; for one person, use person_summary.
Output schemas not documented. LLMs cannot plan downstream tool calls or extract required fields without knowing what spend_summary and signals return. Baseline: 100% of A+ tools have documented return types.
Parameter descriptions lack format constraints. 'dateFrom' and 'dateTo' state 'YYYY-MM-DD, inclusive' in description but no regex pattern or minLength/maxLength in schema. 'scope' description references 'opmetrics://structure' but does not specify valid format (e.g., 'company | project:<UUID> | team:<UUID> | person:<UUID>').
Tool names lack action verb prefix. 'spend_summary' and 'signals' are nouns; stronger names would be 'get_spend_summary' or 'list_signals'. Baseline: 90% of A+ tools start with an action verb (get, list, create, search, update).
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 61 | 2026-07-28+ | v2 |
No error handling guidance in tool definitions. If scope ID is invalid or date range is malformed, LLMs have no recovery path. Descriptions should include: 'If scope not found, call list_scopes() first' or 'Invalid date format, use YYYY-MM-DD'.
Scope parameter accepts opaque IDs (project:<id>, team:<id>, person:<id>) without guidance on how to discover valid IDs. Tool description references 'opmetrics://structure' but does not explain whether a discovery tool exists or how to obtain IDs.