Skip to main content
Glama
Sign In

Nextmail

by sh.nextmail
OverviewDiscussionsAdmin

Get connected mailbox settings

getConnectedMailboxSettings
Read-only

The servers and the kind of sign-in an address needs before it can be connected: the provider, the incoming IMAP server and the outgoing SMTP server. The connection itself needs a password and happens in the app or over the REST API, never through a tool. An Outlook.com or Microsoft 365 address connects in the app with a Microsoft sign-in.

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": {
      "email": "<email>"
    },
    "name": "getConnectedMailboxSettings"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the read-only annotations, the description adds important behavioral context: the connection requires a password and occurs outside tools, and Outlook.com/Microsoft 365 addresses use a Microsoft sign-in. It does not cover auth requirements or rate limits, but it meaningfully adds to the annotation profile.

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

Conciseness3/5

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

The description is three sentences, all relevant, but it is not front-loaded with the action and the first sentence is an awkward noun phrase. It could be tightened for faster scanning.

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?

For a simple getter with one parameter, the description is fairly complete: it lists returned settings, clarifies what the tool does not do, and notes the Microsoft sign-in case. No output schema exists, but the key return fields are mentioned.

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?

Schema coverage is 0% for the single email parameter, and the description only indirectly refers to 'an address' without explaining format or constraints. The parameter is intuitive, but the description does not fully compensate for the missing schema documentation.

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 clearly identifies the resource: provider, IMAP/SMTP servers, and sign-in kind required for an address. It lacks an explicit action verb and does not differentiate from sibling tools like discoverMailboxSettings, but the purpose is still understandable.

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?

It clarifies that connection happens in the app or REST API, never through a tool, which is useful when-not-to-use guidance. However, it does not explicitly say when to use this tool versus siblings such as getConnectedMailbox or discoverMailboxSettings.

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

All Nextmail toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources