log-search-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 | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_logsC | Search application logs on remote servers using grep patterns |
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 1 tool
With only a single tool, there is no possible ambiguity. The tool's purpose is clearly stated and there are no overlapping tools to confuse an agent.
With only one tool, the naming pattern is technically consistent by default, but there is insufficient surface area to establish a clear pattern. The verb_noun convention (search_logs) is sensible and readable.
A single search tool feels extremely thin for a 'log-search MCP server'. The stated domain of searching remote logs typically requires supporting operations like listing log files, fetching specific log content, or filtering by time ranges, which are absent.
The tool surface is severely underdeveloped for the stated purpose. While search is the core operation, there are no complementary tools to browse log files, retrieve specific entries, or inspect log sources, leaving agents with a dead-end workflow.