bt-ops-mcp-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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| open_settingsA | 内置工具，无法关闭；启动或复用本机设置页并返回访问地址。 |
| get_settings_statusA | 内置工具，无法关闭；受限模式下返回未进入业务模式的原因、配置路径和下一步。 |
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 2 tools
open_settings and get_settings_status are clearly distinct: one launches/reuses a settings page and returns a URL, while the other reports the status (why not in business mode, config path, next step). No overlap or confusion.
Both tools follow a verb_noun snake_case pattern (open_settings, get_settings_status), providing a consistent and predictable naming convention.
With only two tools, the server feels thin, especially for a settings-related domain. This is borderline but acceptable for a narrowly-focused utility.
The tool set covers opening settings and checking status but lacks any update, reset, or configuration modification tools. This leaves a significant gap for any agent needing to actually change settings, making the surface incomplete.