Spamshieldpro MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | API 密钥 |
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 |
|---|---|
| check_for_spamC | endpoint for checking form content |
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 tool 'check_for_spam' has a singular, clear purpose that cannot be confused with any other tool in the set.
The single tool name 'check_for_spam' follows a clear verb_noun pattern, and with only one tool, consistency is inherently perfect. There are no other tools to compare against, so no inconsistencies can arise.
A single tool for a server named 'Spamshieldpro' suggests a very limited scope, likely insufficient for comprehensive spam detection or management tasks. This feels thin and may leave obvious gaps in functionality, such as updating spam lists or handling different types of spam checks.
The tool set is severely incomplete for a spam-related domain. With only a 'check_for_spam' tool, there are no operations for managing spam data (e.g., add to blacklist, remove false positives), configuring settings, or handling different spam types, leading to significant gaps that will hinder agent effectiveness.