Strong foundation with 19 well-named tools following verb_noun convention (project_list, bug_search, bug_subscribe). All tools have descriptions (avg 95 chars, within 10-1024 baseline). Input schemas present with typed parameters and descriptions. Tool annotations applied to write/destructive operations (project_subscribe, bug_vote, bug_unsubscribe). Key gaps: output schemas not documented in source; parameter descriptions lack format/constraint details (e.g., 'limit' has no min/max bounds); no enum constraints for vote_kind despite fixed set (ManifestsForMe|FixImportant); error handling guidance minimal.
Get human-readable details for a bug returned by a list or search tool.
Get reference-redacted upstream history entries embedded in a bug card.
Get the current subscription and vote state for a bug.
List recently visible bugboard bugs using first-page dynamic-list summaries.
List bugs subscribed by the configured bugboard user.
List bugs voted by the configured bugboard user.
Output schemas not documented. Tool descriptions state what is returned (e.g., 'human-readable summaries', 'reference-redacted history') but formal output schema definitions are absent from source. LLMs cannot plan downstream tool chains without knowing returned field names and types.
Numeric parameter constraints missing. 'limit' parameters in project_list, bug_list_recent, bug_list_subscribed, bug_list_voted lack min/max bounds. Code shows DEFAULT_LIST_LIMIT=10, MAX_LIST_LIMIT=50, but these are not exposed in parameter descriptions. LLMs may pass invalid values.
Enum constraints not declared for vote_kind. bug_list_voted and bug_vote accept vote_kind with description 'Vote kind: ManifestsForMe or FixImportant' as free-form string, not enum. Should be declared as enum in schema to prevent hallucinated values.
Inferred effective spec: 2025-06-18+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 62 | 2025-06-18+ | v2 |
Return the browser URL for a bug.
Search bugboard bugs by exact bug number or full-text query.
Idempotently subscribe to a bug and verify the resulting state.
Idempotently unsubscribe from a bug and verify the resulting state.
Idempotently remove one kind of bug vote and verify the resulting state.
Idempotently add one kind of bug vote and verify the resulting state.
Check whether the configured 1C bugboard session is authenticated.
List visible versions for a project returned by project_list.
List visible 1C bugboard projects as human-readable summaries.
Return the configured user's subscribed projects as safe bugboard data.
Idempotently subscribe to a project and verify the resulting state.
Idempotently unsubscribe from a project and verify the resulting state.
List bugs for a unique exact version title returned by project_get_versions.
Error handling guidance absent. Tool descriptions do not explain recovery paths (e.g., 'If authentication fails, check BUGBOARD_MCP_* environment variables'). Error responses likely return raw ToolFailure without actionable next steps for LLM.
Parameter reference semantics unclear. Tools accept 'project_ref' and 'bug_ref' but descriptions do not explain whether these are opaque handles, human-readable names, or system IDs. Code shows HandleStore.remember/resolve pattern, but this is not documented for users.