BoJ-server
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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| boj_healthB | Check BoJ server health status |
| boj_menuB | List all BoJ cartridges with their domains, protocols, tiers, and availability |
| boj_cartridgesB | Show the BoJ cartridge matrix — protocol x domain grid showing which cartridges serve which protocol/domain combinations |
| boj_cartridge_infoB | Get detailed information about a specific BoJ cartridge |
| boj_cartridge_invokeC | Invoke a BoJ cartridge operation. Send a command to a specific cartridge for execution. |
| boj_cloud_verpexC | Manage Verpex hosting via cPanel UAPI — domains, DNS, email, databases, SSL, cron, metrics |
| boj_cloud_cloudflareC | Manage Cloudflare resources — Workers, D1 databases, KV namespaces, R2 buckets, DNS zones/records |
| boj_cloud_vercelC | Manage Vercel projects — deployments, domains, environment variables, logs, serverless functions |
| boj_comms_gmailC | Gmail operations — send, read, search emails, manage labels |
| boj_comms_calendarC | Google Calendar operations — list events, create events, check availability |
| boj_ml_huggingfaceC | Hugging Face operations — search models, model info, inference, spaces, datasets |
| boj_browser_navigateC | Navigate Firefox to a URL |
| boj_browser_clickC | Click an element on the page by CSS selector |
| boj_browser_typeC | Type text into an element on the page |
| boj_browser_read_pageB | Read the text content of the current page |
| boj_browser_screenshotB | Take a screenshot of the current page |
| boj_browser_tabsC | List, create, or close browser tabs |
| boj_browser_execute_jsC | Execute JavaScript in the current page context |
| boj_github_list_reposC | List your GitHub repositories |
| boj_github_get_repoC | Get a GitHub repository |
| boj_github_create_issueC | Create an issue on a GitHub repo |
| boj_github_list_issuesC | List issues on a GitHub repo |
| boj_github_get_issueD | Get a specific issue |
| boj_github_comment_issueD | Comment on an issue |
| boj_github_create_prC | Create a pull request |
| boj_github_list_prsC | List pull requests |
| boj_github_get_prC | Get a specific pull request |
| boj_github_merge_prC | Merge a pull request |
| boj_github_search_codeC | Search code on GitHub |
| boj_github_search_issuesC | Search issues and PRs on GitHub |
| boj_github_get_fileC | Get file contents from a repo |
| boj_github_graphqlC | Execute a GitHub GraphQL query |
| boj_gitlab_list_projectsC | List your GitLab projects |
| boj_gitlab_get_projectC | Get a GitLab project |
| boj_gitlab_create_issueC | Create a GitLab issue |
| boj_gitlab_list_issuesC | List GitLab project issues |
| boj_gitlab_create_mrD | Create a merge request |
| boj_gitlab_list_mrsC | List merge requests |
| boj_gitlab_list_pipelinesC | List CI/CD pipelines |
| boj_gitlab_setup_mirrorC | Set up a push mirror |
| boj_researchC | Academic research — search papers, citations, references, authors |
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 41 tools
Tools are generally well-differentiated by domain and action, with clear prefixes like 'boj_browser_', 'boj_github_', and 'boj_gitlab_' organizing them. Some potential confusion exists between similar operations across domains (e.g., 'boj_github_create_issue' and 'boj_gitlab_create_issue'), but the domain prefixes help distinguish them. A few tools like 'boj_cartridge_invoke' and 'boj_cartridge_info' have overlapping purposes but are still distinguishable by their specific functions.
Naming is highly consistent throughout, following a clear pattern of 'boj_[domain]_[action]' with snake_case used uniformly. Verbs like 'create', 'list', 'get', and 'manage' are applied predictably across domains (e.g., 'boj_github_create_issue', 'boj_gitlab_list_issues'). This consistency makes it easy for agents to understand and navigate the toolset without confusion.
With 41 tools, the count is excessive for a single server, making it feel bloated and potentially overwhelming for agents. While the tools cover multiple domains (browser, cloud, GitHub, GitLab, etc.), such a high number suggests poor scoping; it might be better split into separate, more focused servers. This heavy load can hinder agent efficiency and increase misselection risks.
The toolset shows strong coverage across its domains, with comprehensive CRUD operations for GitHub and GitLab (e.g., create, list, get, merge), browser automation, cloud management, and more. Minor gaps exist, such as missing update/delete operations for some resources (e.g., no 'update_issue' for GitLab), but agents can likely work around these. Overall, it supports a wide range of workflows without major dead ends.