Glama MCP Server Search
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_mcp_serversB | Search for MCP servers in the Glama directory using free text queries |
| get_mcp_server_detailsA | Get detailed information about a specific MCP server by namespace and slug |
| get_mcp_server_attributesA | Get available attributes that can be used to filter MCP servers |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Glama MCP Server Search Documentation |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose with no overlap: get_mcp_server_attributes retrieves filterable attributes, get_mcp_server_details fetches specific server information, and search_mcp_servers performs free-text queries. The descriptions make it impossible to confuse which tool to use for each task.
All three tools follow a perfect verb_noun pattern with snake_case: get_mcp_server_attributes, get_mcp_server_details, and search_mcp_servers. The naming is highly predictable and consistent throughout the set.
With only 3 tools, the set feels thin for a search server that might benefit from additional operations like filtering by attributes directly or pagination controls. While the core functions are covered, the count is borderline minimal for the apparent scope.
The tools cover the essential search workflow: getting attributes for filtering, searching servers, and retrieving details. A minor gap exists in not having a tool to directly filter servers using those attributes without free-text search, but agents can work around this by combining tools.