MCP Tool
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 |
|---|---|
| sanD | – |
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 named 'san', there is no possibility of ambiguity or overlap with other tools. The single tool stands alone without any confusion risk.
A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The name 'san' follows no pattern but does not conflict with anything else.
One tool is generally too few for most server purposes, indicating a thin or incomplete surface. Without a description, it's unclear if this minimal set is justified, but it likely represents an extreme mismatch for typical MCP server functionality.
With only one tool and no description provided, it is impossible to assess coverage of any domain. The surface is severely incomplete, as no operations or lifecycle can be inferred, making it highly likely to cause agent failures.