Skip to main content
Glama

E-Mail-Postfächer anzeigen

get_email_accounts
Read-only

E-Mail-Konten einer Domain auflisten (live von Plesk): Adresse, Speicherkontingent, eingerichtete WEITERLEITUNG und ALIASE. Das ist das lesende Gegenstück zu set_email_forwarding und set_email_alias — vorher war über den Chat nicht zu sehen, wohin die Post eines Postfachs geht oder unter welchen weiteren Adressen es erreichbar ist. Steht bei einem Konto keine Weiterleitung, ist das eine abgerufene Auskunft ("es ist keine eingerichtet"), keine fehlende Angabe; dasselbe gilt für Aliase. Das Weiterleitungsziel zeigt häufig auf eine FREMDE Domain und wird genau so ausgegeben, wie es eingetragen ist. Dazu steht je Konto der Stand der ABWESENHEITSNOTIZ (an mit Enddatum, aus, abgelaufen; "Stand nicht lesbar" ist keine Aussage) — das lesende Gegenstück zu set_email_autoreply; der Text der Notiz wird nicht ausgegeben. Bei mehr als 30 Postfächern fehlt diese Angabe.

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>"
    },
    "name": "get_email_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDie Domain, z. B. example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the readOnly/non-destructive annotations by disclosing that data is fetched live from Plesk, that a blank forwarding field means 'none configured' rather than missing data, that forwarding targets may point to foreign domains and are returned verbatim, and that autoreply status has specific states ('an mit Enddatum, aus, abgelaufen', 'Stand nicht lesbar'). It also notes the note text is not returned and that the autoreply field is absent for accounts beyond 30 mailboxes.

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?

The description is front-loaded with purpose and the most important edge-case semantics. It is fairly long, but nearly every sentence carries useful behavioral information (forwarding semantics, external targets, autoreply states, >30 mailbox limit). Slight redundancy around 'dasselbe gilt für Aliase' keeps it from a 5.

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

Completeness5/5

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

For a single-parameter read tool with no output schema, the description is unusually complete: it enumerates returned fields, defines null/blank semantics, discloses data-source freshness, and documents a size-based limitation. The annotations already cover safety, and the description fills the remaining behavioral and interpretation gaps.

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 only one parameter and schema description coverage is 100%, so the schema already documents 'domain' with an example. The description refers to 'einer Domain' but adds no syntax, format, or constraint beyond what the schema provides. Baseline 3 is appropriate.

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 ('auflisten') and resource ('E-Mail-Konten einer Domain') and lists the exact fields returned (Adresse, Speicherkontingent, Weiterleitung, Aliase, Abwesenheitsnotiz). It explicitly distinguishes itself from sibling mutation tools set_email_forwarding, set_email_alias, and set_email_autoreply, so an agent can route correctly.

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?

Clearly frames itself as the reading counterpart to set_email_forwarding and set_email_alias, implying when to use it. It also explains a key interpretation rule (missing forwarding means 'none configured', not missing data) and notes the >30 mailbox limitation. It stops short of explicit 'use this instead of X when Y' phrasing, but the context is strong.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources