Remove the SMTP email configuration in Metabase to reset email settings.
Clear the SMTP email configuration in Metabase
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "clear_email"
}
}| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the full burden. It states 'clear' implies a destructive action, but it does not disclose whether it disables email, requires authentication, or is reversible. This is insufficient for a mutation tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise (one sentence) but under-specified. It lacks context that would be useful for an AI agent, such as effects and usage. It is not overly verbose but could be improved with more detail.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool is a clear operation with no output schema and no annotations, the description is incomplete. It does not explain the consequences, such as whether email functionality stops working or the configuration reverts to defaults. This is inadequate for a destructive tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has no parameters (0 params), so schema coverage is 100%. According to the guidelines, baseline is 4 when there are no parameters. The description does not need to add parameter info.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Clear') and the resource ('the SMTP email configuration in Metabase'). It distinguishes from siblings like 'configure_email' (which sets up) and 'test_email'. However, it could be more specific about what 'clear' means (e.g., reset to default, delete settings).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool vs alternatives. For instance, it does not mention that this should be used to disable email or revert to default, nor does it contrast with 'configure_email' or 'update_setting'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.