eazy-ba
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ba_initD | Scaffold the docs/ba BA docs tree. |
| ba_session_startA | Start or resume a BA session (mode: discovery | stabilize | change | ground). For ground mode, pass readScope: the user-supplied paths/globs (relative to projectRoot) the BA may read; it is persisted to the session and bounds what ba_ground can auto-accept. |
| ba_assessB | Analyze current state and return the questions to ask the user. Writes no BA documents (it only updates session state). |
| ba_record_answersC | Record the user's answers as traceable decisions. |
| ba_applyB | Materialize/update documents from recorded decisions. Every artifact must cite derived_from decisions. |
| ba_statusB | Report open questions, gaps, pending decisions, the open coverage plan, and stability. |
| ba_planA | Declare or retire agent/user coverage topics (the visible, steerable coverage plan on top of the floor). Declaring is idempotent; retiring stops a topic from gating stability. Returns the current open plan. |
| ba_finalizeA | Promote every draft BA document (persona/fr/nfr/use-case/story/glossary/tech-surface) to status 'reviewed' in one batch — the clean 'here are your docs' step. Idempotent and repeatable: a second call with nothing in draft is a no-op, and it promotes again after a change loop re-opens work. Only changes status; never touches backing. Returns what was promoted. |
| ba_impactA | For a mid-project change: report blast radius, conflicts, severity, consequences, and change questions for the given target ids. Creates nothing. |
| ba_groundA | Ground flow (ground session only): record code observations the host agent read. Each is { fact_kind, claim, anchors }. Auto-accepts ONLY existence facts the server can re-verify (entity-exists | dependency-present) whose anchors resolve on disk and sit inside the session read scope — recorded as confirmed/code-verified. Everything else (route/middleware/config-key, anything mislabeled, out-of-scope or unresolvable anchors) is recorded as an inferred+open observation that the user must confirm. Idempotent by (anchors+claim). |
| ba_getC | Get one artifact by id. |
| ba_listC | List artifacts filtered by type/status/priority/tag. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/God1n/eazy-ba'
If you have feedback or need assistance with the MCP directory API, please join our Discord server