Skip to main content
Glama
@marlinjai/email-mcp

@marlinjai/email-mcp

by marlinjai

email_test_account

Tests an email account connection using its account ID to verify credentials and provider connectivity before searching, sending, or organizing mail.

Instructions

Test an email account connection

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": {
      "accountId": "<accountId>"
    },
    "name": "email_test_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountIdYesID of the account to test

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.11.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: it does not say whether the test is read-only or mutates stored account state, whether it performs live network/SMTP/IMAP authentication, whether it is rate-limited or slow, or what success/failure looks like. For a zero-annotation tool the single phrase 'Test an email account connection' is thin.

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

Conciseness4/5

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

A single short, front-loaded phrase with zero padding or redundancy. It is efficient, though its brevity reflects under-specification rather than disciplined economy.

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

Completeness2/5

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

With no annotations and no output schema, the description must compensate, but it never indicates what the tool returns (boolean, status object, error message) or whether the operation is safe to call repeatedly. For a diagnostic tool whose entire value is its result semantics, that is a material gap.

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?

There is one parameter (accountId) at 100% schema description coverage ('ID of the account to test'), so the schema already does the work. The description adds no meaning beyond it — no note on where the ID comes from (e.g. email_list_accounts) or whether an unknown ID errors.

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

Purpose4/5

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

The description states a specific verb plus resource: 'Test an email account connection'. That is unambiguous and clearly distinct from the account-management siblings such as email_add_account or email_remove_account, but it does not explicitly differentiate itself from anything else (no other test/diagnostic tool appears among the siblings).

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?

Usage is only implied by the word 'Test' — an agent can infer it is used to verify credentials/connectivity for an account identified by accountId. There is no explicit statement of when to prefer it (e.g. after email_add_account, or instead of email_list_accounts when checking health) and no guidance on what a failure means or what to do next.

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