Skip to main content
Glama
owlpost

owlpost

list_accounts

Read-onlyIdempotent

Lists the mail accounts configured in owlpost, returning names, email addresses, providers, IMAP/SMTP hosts, and sent-mail auto-save status for use with other tools.

Instructions

List the mail accounts configured in owlpost's accounts.toml.

Returns one entry per account with its name (the value to pass as account to every other tool), email address, provider (icloud, gmail or generic), IMAP/SMTP hostnames and whether sent mail is auto-saved. Passwords and password sources are never included. Takes no arguments and does not contact any mail server.

Tool call template

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": "list_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.3.0
    • addedOutput schema / $defs
      Added value: +{
      +  "AccountInfo": {
      +    "properties": {
      +      "auto_save_sent": {
      +        "title": "Auto Save Sent",
      +        "type": "boolean"
      +      },
      +      "email": {
      +        "title": "Email",
      +        "type": "string"
      +      },
      +      "imap_host": {
      +        "title": "Imap Host",
      +        "type": "string"
      +      },
      +      "name": {
      +        "title": "Name",
      +        "type": "string"
      +      },
      +      "provider": {
      +        "title": "Provider",
      +        "type": "string"
      +      },
      +      "smtp_host": {
      +        "title": "Smtp Host",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "name",
      +      "email",
      +      "provider",
      +      "imap_host",
      +      "smtp_host",
      +      "auto_save_sent"
      +    ],
      +    "title": "AccountInfo",
      +    "type": "object"
      +  }
      +}
    • addedOutput schema / properties / result / items / $ref
      Added value: +"#/$defs/AccountInfo"
    • removedOutput schema / properties / result / items / additionalProperties
      Removed value: -true
    • removedOutput schema / properties / result / items / type
      Removed value: -"object"
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing the data source (a local accounts.toml), that no mail server is contacted, and — security-relevant and not in annotations — that passwords and password sources are never included. The no-network fact partly overlaps openWorldHint=false, so it is strong rather than exceptional.

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?

Front-loaded with the verb and resource, then a tight enumeration of return fields, then two clarifying limitations. No filler sentences; every clause carries information an agent needs.

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?

An output schema exists, yet the description still summarises the entry shape and explicitly names the field that unlocks all other tools. For a zero-argument, read-only discovery tool, nothing further is required.

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?

The tool takes zero parameters, which sets the baseline at 4. The description confirms 'Takes no arguments', consistent with the empty 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?

States a specific verb and resource ('List the mail accounts configured in owlpost's accounts.toml') and enumerates exactly what each entry contains (name, email, provider, IMAP/SMTP hosts, sent-mail auto-save). It is unmistakably distinct from every sibling tool, which all operate on folders or messages rather than the account config.

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?

Explicitly routes the agent: the returned `name` is 'the value to pass as `account` to every other tool', which tells an agent to call this first before search_messages, read_email, etc. No when-not guidance is given, but for a zero-argument config readout there is no realistic alternative to exclude.

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