LobsterMCP
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| resolve-topicA | Find OpenClaw documentation topics matching your query. Returns topic IDs to use with query-config-docs. Topics include: models, providers, configuration, gateway, agents, sessions, tools, skills-plugins, channels, install, concepts, security-sandbox, and debugging. |
| query-config-docsA | Get detailed OpenClaw documentation and code examples. Use resolve-topic first to find the right topicId, or search directly with a query. |
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 2 tools
The two tools have clearly distinct purposes: resolve-topic finds topic IDs, and query-config-docs retrieves detailed documentation. Though query-config-docs can also search directly, the workflow is still unambiguous and each tool's role is well-defined.
Both tool names follow the same verb-noun pattern using hyphens: resolve-topic and query-config-docs. This is consistent and readable, with a clear action-then-object structure.
With only two tools, the server feels minimal but not unreasonable for a focused documentation lookup scope. It sits at the thin end of the scale, barely maintaining a meaningful surface.
The tools cover topic discovery and content retrieval, but there is no way to list all available topics or navigate documentation structure beyond keyword matching. The direct search capability mitigates the gap, but some exploration workflows remain unsupported.