ToolMux
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_tool_schemaA | Get full description and inputSchema for a specific tool. |
| get_tool_countA | Get count of available tools by server. |
| list_all_toolsA | List all tool names and descriptions grouped by server. Optionally filter by server name. |
| filesystemC | Tools: filesystem (Local filesystem access - read, write, and manage files) |
| brave-searchC | Tools: brave-search (Web search using Brave Search API) |
| manage_serversB | Manage ToolMux backend MCP servers. Actions: list, add, remove, validate, test, retry. Examples: manage_servers(action="list") manage_servers(action="add", name="my-mcp", command="my-mcp-server", description="My MCP") manage_servers(action="remove", name="my-mcp") manage_servers(action="validate") manage_servers(action="test", name="my-server") manage_servers(action="retry", name="aws-sentral-mcp") |
| optimize_descriptionsA | Optimize ToolMux tool descriptions using your intelligence as the LLM. Produces higher-quality descriptions than the auto-generated algorithmic ones. Actions: status — Check if descriptions have been optimized or are still algorithmic. generate — Returns all tools with their full descriptions. Read them and generate concise (<60 char) versions. save — Save your optimized descriptions for a server. Workflow:
|
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
Most tools have clearly distinct purposes: introspection (get_tool_schema, get_tool_count, list_all_tools), server management (manage_servers), and description optimization (optimize_descriptions). However, 'filesystem' and 'brave-search' are ambiguous as they appear to be single tools but actually represent bundled servers, making their usage boundaries unclear.
Five tools follow a consistent verb_noun pattern (get_tool_schema, get_tool_count, list_all_tools, manage_servers, optimize_descriptions). The remaining two, 'filesystem' and 'brave-search', are bare nouns with hyphens, breaking the convention and reducing consistency.
Seven tools is a reasonable number for a server management and introspection tool. The inclusion of 'filesystem' and 'brave-search' as standalone tools is somewhat unusual but does not significantly bloat the count.
The tool set covers core operations: listing tools, fetching schemas, counting tools, managing servers (list/add/remove/validate/test/retry), and optimizing descriptions. A notable gap is the lack of an update operation for server configurations, but most common workflows are supported.