Agent Stack Directory
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENT_STACK_DATA_URL | No | Where to fetch the dataset | https://agentstackdirectory.com/data.json |
| AGENT_STACK_DATA_FILE | No | Read a local JSON file instead, for offline use, e.g. data/agent-stack-directory.json |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_toolsA | Search Agent Stack Directory for AI agent infrastructure tools by keyword, with optional category and open-source filters. Omit query to list every tool in a category. |
| get_toolA | Get the full listing for one tool by slug or name: summary, official site, open-source flag, last link check, and the alternatives in its category. |
| compareA | Compare 2 to 4 tools side by side by slug or name. Returns a table, notable differences and the head-to-head page when one exists. |
| list_categoriesA | List every category (layer of the agent stack) with its key, description and 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
The four tools occupy clearly distinct roles: search_tools for discovery, get_tool for single-item detail, compare for side-by-side evaluation, and list_categories for taxonomy browsing. There is no functional overlap, so an agent can select unambiguously.
Three tools follow a clean verb_noun pattern (search_tools, get_tool, list_categories) in consistent snake_case. The lone 'compare' is a bare verb that breaks the pattern slightly, but it remains readable and idiomatic.
Four tools is well-scoped for a read-only directory server, with each tool earning its place. It is on the lean side but not thin enough to feel incomplete for the domain.
The surface covers the core directory workflows: browse categories, search/filter tools, fetch full listings, and compare tools. Minor gaps like global cross-category listing or browsing alternatives without a specific category exist, but agents can work around them.