The Toolbox MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TAVILY_API_KEY | No | Tavily API key used for the toolbox_research tool's real-time web enrichment (required for that tool to function). | |
| LANGSMITH_API_KEY | No | Optional LangSmith API key for custom tracing. | |
| LANGSMITH_PROJECT | No | Optional LangSmith project name for tracing. | |
| LANGSMITH_ENDPOINT | No | Optional LangSmith endpoint URL for tracing. |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| toolbox_searchA | Find installed tools by literal words, with optional source/category filters and bounded pagination. |
| toolbox_describeA | Return up to 50 indexed records for an exact tool name across package managers. |
| toolbox_inventoryA | Show inventory size, source scan timestamps/failures, and categories without scanning or executing tools. |
| toolbox_researchB | Enrich tool information with real-time web search via Tavily. Combines Librarian's indexed data with Tavily web search for up-to-date documentation, GitHub links, and usage examples. |
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 4 tools
Each tool has a distinct role: search (fuzzy word lookup), describe (exact-name multi-source lookup), inventory (metadata/status), and research (web enrichment). Search vs describe slightly overlap since both return tool records, but the 'literal words' vs 'exact name' distinction is stated clearly enough to guide selection.
All four tools follow a consistent toolbox_<verb> snake_case pattern (search, describe, inventory, research). Predictable and easy to map to intent.
Four tools is on the lean side but each covers a genuine stage of discovery (scan status, find, detail, enrich). No redundant tools, though the surface feels slightly thin for a 'toolbox'.
For a discovery/lookup server the lifecycle (inventory status -> search -> describe -> research) is covered without dead ends. Missing install/execute/update operations, but those appear outside the stated read-only scope.