ToolBox
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENROUTER_API_KEY | No | API key for OpenRouter, used by Jev for routing. If not provided, ToolBox falls back to keyword search. |
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 |
|---|---|
| find_toolsA | Find the best tools for a task across every server connected to ToolBox. Pass the user's request, or the current sub-task, in plain language. Returns tool_ids with confidence, effect (read/write), gate (allow/confirm/block) and input_schema. Then run one with call_tool. |
| call_toolA | Run a tool on a server connected to ToolBox. tool_id comes from find_tools or browse_tools, e.g. "screener/get_peers". arguments must match that tool's input_schema. Actions that change things may ask the user to approve them first; blocked actions never run. |
| browse_toolsA | Look through the tool catalog when find_tools didn't surface what you need. No arguments: list the servers. server="kite": list that server's tools. tool_id="kite/get_ltp": full description and input_schema for one tool. |
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 3 tools
find_tools and browse_tools both aid discovery, but descriptions clearly distinguish them: find_tools uses natural-language search, while browse_tools is a fallback catalog browser. call_tool is unambiguously for execution, so only minor overlap exists.
All names use snake_case and follow a verb_noun pattern (find_tools, call_tool, browse_tools). The only inconsistency is call_tool using singular 'tool' while the others use plural 'tools', which is a minor deviation.
Three tools form a minimal, well-scoped interface for a meta-server: search for tools, execute a tool, and browse the catalog when search fails. Each tool earns its place without redundancy.
The surface covers the full lifecycle of tool discovery and invocation: find_tools returns tool IDs with schemas, call_tool executes with arguments, and browse_tools provides fallback listing and detailed descriptions. No obvious operational gaps exist for this domain.