bst-avl-mcp
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 |
|---|---|
| reset_treeA | Reset the specified tree (bst or avl) to be empty. |
| insert_nodeC | Insert a key into the specified tree. |
| delete_nodeC | Delete a key from the specified tree. |
| search_nodeC | Search for a key in the specified tree. |
| print_treeB | Get a visual representation of the tree structure. |
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 5 tools
Each tool performs a distinct operation on the tree: reset, insert, delete, search, and print. No two tools overlap in purpose, making selection unambiguous.
All tool names follow a consistent verb_noun pattern (reset_tree, insert_node, delete_node, search_node, print_tree). The convention is predictable and easy to read.
Five tools are well-scoped for a BST/AVL tree server, covering the essential operations without bloat. Each tool clearly earns its place.
The surface covers the core lifecycle: reset, insert, delete, search, and visualize. Minor gaps exist for auxiliary queries like tree height, size, or traversal order, but these are not essential for basic tree manipulation.