LSD MCP Server
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 |
|---|---|
| brave_searchC | Search Brave for possibly relevant links to a query |
| run_lsdD | – |
| find_tripsD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| lsd_research | |
| huxley |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| lsd_docs |
TDQS
Scored across 3 tools
The tools have unclear boundaries and overlapping purposes. 'brave_search' and 'find_trips' could both be interpreted as search tools, with the latter's lack of description making it ambiguous whether it searches for trips or performs another function. 'run_lsd' is completely opaque without a description, potentially overlapping with execution or processing roles.
The naming is mixed but readable. 'brave_search' and 'find_trips' follow a verb_noun pattern, while 'run_lsd' uses a verb_prefix style. There is no chaotic mixing of cases, but the conventions are not fully consistent across all tools.
With only 3 tools, the server feels thin for a general-purpose 'LSD MCP Server', suggesting an incomplete surface. The lack of descriptions for two tools makes it hard to assess scope, but the count is borderline too few for meaningful coverage of any substantial domain.
The server is severely incomplete. Based on the tool names, it appears to cover search and execution, but with no descriptions for 'find_trips' and 'run_lsd', there are significant gaps. It lacks any CRUD operations, lifecycle management, or clear domain coverage, making it impossible for agents to perform coherent workflows.