Backlog Buddy MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| validate_storyA | Checks one user story against INVEST (Independent, Negotiable, Valuable, Estimable, Small, Testable) and acceptance-criteria quality rules. Returns a 0–100 score, a verdict (ready / needs-work / not-ready) and specific findings with suggested fixes. Use it on every story you draft before showing it to the user. |
| validate_backlogA | Checks several user stories at once: each gets an INVEST report, plus a summary with average score, how many are ready, total points and possible duplicates. |
| suggest_splitsA | Given a story or feature that is too big, suggests splitting patterns that fit it (workflow steps, CRUD operations, business rules, data variations, interfaces, happy path first, defer performance, user roles, spikes), each with how to apply it and an example. |
| export_backlogA | Formats finished stories as Markdown (for docs or a README), plain CSV (for spreadsheets), or jira-csv (columns laid out for Jira's CSV importer: Summary, Issue Type, Description, Story Points, Labels). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| feature_to_stories | Guides the assistant from a feature brief to a checked, export-ready set of user stories. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| invest-guide | INVEST, acceptance criteria and story splitting, in one page |
TDQS
Scored across 4 tools
Each tool targets a distinct operation: single-story validation, batch validation, splitting suggestions, and export. The only near-overlap (validate_story vs validate_backlog) is explicitly disambiguated by 'one user story' vs 'several user stories at once' in the descriptions.
All four names follow a uniform snake_case verb_noun pattern (validate_story, validate_backlog, suggest_splits, export_backlog) with semantically accurate verbs. No mixed conventions or vague verbs.
Four tools is on the lean side but each covers a real step in the story-writing workflow (validate, validate-in-bulk, split, export). It sits at the low end of the comfortable 3-15 range without feeling padded or redundant.
Validation, splitting, and export round out the stated purpose well, and the agent supplies the drafting in-context. Minor gaps exist: no tool to persist/retrieve a backlog or to generate acceptance criteria or story points, so exported data must be assembled entirely by the model.