Skip to main content
Glama
Sign In
mx-route-mcp

mx-route-mcp

by MauiGrowth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Remove spam blacklist entry

remove_spam_blacklist_entry
DestructiveIdempotent

Remove an entry from an account-wide spam blacklist to allow previously blocked senders. Provide the domain and exact entry, and confirm before destructive changes.

Instructions

Removes an entry from the account-wide spam blacklist. The domain argument must be one you own, but the lists themselves are account-wide. Destructive: confirm with the user before calling.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "<domain>",
      "entry": "<entry>"
    },
    "name": "remove_spam_blacklist_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
entryYesThe exact entry to remove, e.g. *@trusted.com
domainYesDomain name on the MXroute account, e.g. example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, yet the description still adds value: it tells the agent to confirm with the user before calling, and warns that the lists are account-wide so a removal is not scoped to the given domain. It does not say what happens if the entry is absent, which is why it stops at 4.

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?

Three short sentences, front-loaded with the operation and scope, followed by the ownership caveat and the safety directive. No filler.

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

Completeness4/5

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

No output schema and no annotations on return behavior, but for a delete operation the description covers scope, prerequisites, and the destructive-action guidance an agent needs. Minor gap: it doesn't state behavior when the entry doesn't exist (idempotency semantics).

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning to the 'domain' parameter: it is a domain you own used to authorize the call, while the list itself is account-wide. That clarifies an otherwise confusing ownership/scope split the schema does not express.

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?

States a specific verb ('Removes') plus resource and scope ('an entry from the account-wide spam blacklist'), which cleanly separates it from remove_spam_whitelist_entry and the other remove_* siblings. An agent can identify the operation without opening the schema.

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

Usage Guidelines4/5

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

Gives clear context for invocation: the domain must be owned by the caller and the user should be consulted before calling. It does not name an alternative or explain when removal is inappropriate versus, say, updating spam settings, so it falls short of the explicit alternatives required for a 5.

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

Deploy Server

Other Tools