Skip to main content
Glama
mail-mcp-server

mail-mcp-server

get_vacation

Retrieve the current vacation responder settings for a connected mailbox to check auto-reply status and configuration before making changes.

Instructions

The vacation responder's current settings.

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": {
      "mailbox": "<mailbox>"
    },
    "name": "get_vacation"
  }
}

Input Schema

NameRequiredDescriptionDefault
mailboxYesA connected mailbox address (see list_mailboxes)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.5/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full burden, yet it only says the settings are "current." It does not disclose whether this requires mailbox-scoped auth, what happens if no responder is configured, or whether the result reflects all mailboxes or one.

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?

It is a single short fragment with no filler, but it is under-specified rather than concise: the sentence leaves out the action verb and any scope information that would make it actionable.

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

Completeness2/5

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

With no annotations and no output schema, the description is the only place to explain what is returned (e.g., enabled state, subject, date range), and it says nothing. For a config-read tool paired with a mutation sibling, that is a meaningful gap.

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?

Only one parameter exists and schema description coverage is 100%, with the schema itself pointing at list_mailboxes for valid addresses. The description adds no meaning beyond that, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The fragment "The vacation responder's current settings" identifies the resource and implies a read, but never states a verb and largely restates the tool name get_vacation. It gives no signal distinguishing it from the sibling plan_set_vacation, which presumably mutates the same object.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance at all: nothing says to call this before plan_set_vacation to inspect existing configuration, and no prerequisites or exclusions are given. The agent must infer the read/write split with plan_set_vacation from names alone.

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