Skip to main content
Glama
Sign In

Nextmail

by sh.nextmail
OverviewDiscussionsAdmin

List calendar logins

listCalendarLogins
Read-only

The calendar sign-ins of a person: the logins calendar and contacts apps use over CalDAV and CardDAV, which belong to the person rather than to an address and never open mail. Each has a name, a username starting with cal-, the last four letters of its password, who made it and when an app last used it. The passwords are never shown again.

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

Input Schema

NameRequiredDescriptionDefault
memberNoThe member id of the person it is for, as listWorkspaceMembers gives it. Leave it out for your own. Another member needs the workspace owner or a role that manages members.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior5/5

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

Annotations already establish this as a read-only, non-destructive operation, and the description adds substantial context beyond them: the logins belong to the person rather than an address, do not open mail, and carry name, cal- username, password suffix, creator, and last-use metadata. The note that passwords are never shown again is especially useful behavioral/security context.

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 the resource definition and then gives useful return-field and security details. It is somewhat dense in the first sentence but contains no obvious filler; the closing password note earns its place.

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 simple read-only list tool with one optional parameter, no output schema, and annotations that cover safety, the description is complete enough. It explains what the records represent and what fields they contain, while the schema covers the member parameter and permissions.

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 single optional member parameter is fully documented in the schema, including its default behavior and permission requirements. The description only reinforces that these logins are 'of a person' and does not add syntax or meaning beyond what the schema already provides.

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 as calendar sign-ins/logins used by calendar and contacts apps over CalDAV/CardDAV, for a person rather than an address. It distinguishes the resource from mail and address-based logins, but does not explicitly name sibling tools such as createCalendarLogin or revokeCalendarLogin.

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 implied by the list-style title and by the description of what calendar logins are, but the description does not explicitly state when to use this tool versus alternatives. It gives useful domain context that helps separate calendar logins from address logins or mail, yet no clear when/when-not guidance is provided.

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