Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
WBSO_DIRNoPath to WBSO documentation directoryCurrent working directory

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

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
analyze_wbso_relevanceC

Analyze whether code, commits, or work description is relevant to the WBSO project.

classify_workC

Classify work into the appropriate WBSO technical challenge area

check_commit_wbsoC

Check if a git commit should be logged as WBSO work

get_wbso_criteriaB

Get the full WBSO project criteria and technical challenges

log_researchB

Log a research entry to WBSO documentation

log_developmentC

Log a development entry to WBSO documentation

log_timeB

Log time spent on WBSO R&D work

get_wbso_statusB

Get current WBSO documentation status

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 8 tools

Disambiguation2/5

The tools analyze_wbso_relevance, classify_work, and check_commit_wbso all serve to determine whether work qualifies as WBSO and how to categorize it, creating significant overlap. While descriptions differ slightly (relevance check, classification, commit-specific check), an agent could easily misselect among them.

Naming Consistency4/5

All tool names follow a snake_case verb_noun pattern (analyze_, classify_, check_, get_, log_), which is consistent. Minor inconsistency exists in whether 'wbso' appears in the noun part (analyze_wbso_relevance, get_wbso_criteria vs. classify_work, log_time), but overall the pattern is clear and predictable.

Tool Count5/5

With 8 tools, the server is well-scoped for WBSO management, covering analysis, classification, logging, and status retrieval without unnecessary redundancy. The number feels appropriate for the domain and each tool appears to contribute to the workflow.

Completeness4/5

The tool set covers the core WBSO workflow: checking relevance, classifying work, logging research/development/time, and viewing criteria/status. Minor gaps exist—such as no update or delete operations for logged entries—but for the apparent purpose of documentation and tracking, the surface is reasonably complete.

Maintenance

ActivityInactive
ResponsivenessUnresponsive