IsItDown 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_website_statusC | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| echo_prompt | Check the status of a website. Args: website (str): The website to check. Returns: str: A message indicating the status of the website. |
| informal_prompt | Check the status of Facebook using informal language. |
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_website_status' has a clear, distinct purpose that cannot be confused with any other tool in this set.
The naming follows a consistent verb_noun pattern ('get_website_status'), and with only one tool, there is no inconsistency to evaluate. The naming convention is clear and appropriate for the tool's function.
A single tool is too few for most server purposes, as it limits functionality and can lead to dead ends. For a website status checking server, additional tools like checking multiple sites, monitoring history, or getting detailed status information would be expected to provide a more complete surface.
The tool set is severely incomplete for the domain of website status checking. While 'get_website_status' covers a basic check, there are significant gaps such as batch checking, historical data retrieval, or status monitoring over time, which agents might need for more complex workflows.