fetch-log-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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch_logsB | 从指定的IP地址获取日志内容 |
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 or overlap. The tool's purpose is uniquely defined by its name and description.
The sole tool name 'fetch_logs' follows a clean verb_noun pattern, matching the server name 'fetch-log-mcp-server'. Even with one tool, the naming is predictable and consistent.
The server has exactly one tool, which falls below the typical well-scoped range of 3-15 tools. It is narrowly focused on fetching logs, so it feels thin but not completely unreasonable for a single-purpose utility.
The tool surface is severely limited, offering only 'fetch_logs' with no supporting operations like listing available log sources, filtering by time or type, or handling failures. For a logging domain, this leaves significant gaps that could hinder an agent's workflow.