Skip to main content
Glama
Sign In
mail-calendar-mcp

mail-calendar-mcp

by mathewcsims
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

mail_get_account

Read-onlyIdempotent

Retrieve details for a single Mail account by providing its account name. Works with Apple Mail on macOS to get account properties.

Instructions

Get details for a single Mail account by name.

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": {
      "accountName": "<accountName>"
    },
    "name": "mail_get_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNameYesMail account name, e.g. as shown in mail_list_accounts

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, which are consistent with 'get details'. The description does not add extra behavioral context, but with strong annotations this is acceptable.

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?

A single, well-structured sentence with no wasted words. The key information is front-loaded.

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

Completeness3/5

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

Given the tool's simplicity and good annotations, the description covers the basic purpose and input, but omits any description of the return value or output format, which an agent would need to know for full understanding.

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 100% and the only parameter 'accountName' has a clear description. The tool description merely echoes 'by name', adding no new meaning beyond the 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?

The description clearly states the action ('get details'), the resource ('a single Mail account'), and a key parameter ('by name'). It effectively distinguishes from siblings like mail_list_accounts and mail_get_account_stats.

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?

The description implicitly indicates when to use (when needing details for one specific account), but does not provide explicit when-not or alternative tools. However, the context from sibling names helps.

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

Deploy Server

Other Tools