yala
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 |
|---|---|
| find_toolsA | Search the yala toolkit's 500+ standalone CLI utilities by task (e.g. 'diff openapi specs', 'redis memory', 'gfs retention'). Returns ranked matches with descriptions. Start here. |
| tool_infoA | Full detail for one yala tool: description, example commands, live --help, and whether it mutates state. Use before run_tool. |
| run_toolA | Execute a yala tool from the toolkit root and return exit code, stdout, stderr, and timing. Args are an argv list (no shell). Tools marked mutates=true support --dry-run — prefer it first. |
| list_categoriesA | Overview of every yala toolkit category with tool counts. |
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 purpose: find_tools searches for utilities, tool_info provides details on a specific tool, run_tool executes a tool, and list_categories gives an overview. No overlap or ambiguity.
All tool names follow a consistent lower_snake_case pattern with a clear verb or action prefix (find, tool_info, run, list). The naming is uniform and predictable.
With only 4 tools, the set is tightly scoped to the server's purpose of discovering, inspecting, and running CLI utilities. Each tool earns its place without redundancy.
The toolset covers the full workflow: discovering tools (find_tools, list_categories), getting details (tool_info), and executing them (run_tool). There are no missing operations for the stated purpose.