@bldbl/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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_project_contextD | – |
| get_next_taskD | – |
| start_taskD | – |
| update_progressD | – |
| complete_taskD | – |
| create_discussionD | – |
| health_checkD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
The tools have distinct purposes with minimal overlap: 'complete_task' and 'start_task' are clearly different lifecycle stages, while 'get_next_task', 'get_project_context', and 'update_progress' serve unique informational or update functions. However, 'create_discussion' might be ambiguous in relation to task management, as it could overlap with task-related communication.
All tool names follow a consistent verb_noun pattern using snake_case, such as 'complete_task', 'create_discussion', and 'get_next_task'. This uniformity makes the tool set predictable and easy to understand, with no deviations in naming conventions.
With 7 tools, the count is well-scoped for a task or project management server. It covers core operations like starting, completing, and tracking tasks, along with auxiliary functions like health checks and discussions, without being overly sparse or bloated.
The tool set covers basic task lifecycle (start, complete, progress update) and project context, but lacks obvious operations like listing tasks, updating task details, or deleting tasks. This creates minor gaps that agents might need to work around, though core workflows are partially supported.