Skip to main content
Glama
wyre-technology

spamtitan-mcp

spamtitan_get_queue

Retrieve the email quarantine queue to view quarantined messages with sender, recipient, subject, and quarantine reason. Filter by sender, recipient, subject, or reason for targeted management.

Instructions

List the email quarantine queue. Returns quarantined messages with sender, recipient, subject, and reason for quarantine.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination (default: 1)
per_pageNoNumber of results per page (default: 50, max: 200)
senderNoFilter by sender email address
recipientNoFilter by recipient email address
subjectNoFilter by subject (partial match)
reasonNoFilter by quarantine reason (e.g. spam, virus, policy)
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, and the description does not disclose behavioral traits such as authentication needs, rate limits, or side effects. As a read-only tool, it is acceptable but lacks transparency about any constraints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences long, concise, and directly states the purpose and return fields. Every word is necessary, and it is easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool lacks an output schema, so the description should ideally detail the response structure. While it mentions returned fields, it omits pagination details, metadata, or array structure, leaving the agent with incomplete information for processing results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already describes all 6 parameters with 100% coverage. The description briefly lists fields but adds no additional meaning beyond what is in the schema, so it meets the baseline expectation for a high-coverage schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'list' and the resource 'email quarantine queue', specifying the fields returned (sender, recipient, subject, reason). It is distinct from sibling tools like spamtitan_delete_message or spamtitan_release_message, which perform different actions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for viewing quarantined emails but does not provide guidance on when to use this tool versus alternatives. It lacks explicit context for when to use filters or pagination, and does not mention any prerequisites or limitations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wyre-technology/spamtitan-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server