LGTM 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 |
|---|---|
| get_lgtmB | Get LGTM image and show markdown code and imageurl. |
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 one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'get_lgtm' has a clearly defined and distinct purpose, so an agent cannot misselect between non-existent alternatives.
The naming follows a consistent verb_noun pattern with 'get_lgtm', and since there is only one tool, there is no inconsistency to evaluate. The naming is clear and predictable for the single tool present.
A single tool is too few for most server purposes, as it limits functionality and suggests a very narrow scope. While it might be appropriate for a trivial utility, it feels thin and underdeveloped for a server named 'LGTM MCP Server', which implies more comprehensive LGTM-related operations.
The server is severely incomplete for handling LGTM operations. With only a 'get_lgtm' tool, there are obvious gaps such as creating, updating, deleting, or listing LGTMs, and no coverage of related workflows. This will likely cause agent failures when more complex tasks are required.