Skip to main content
Glama

Mailbox info

get_mailbox_info
Read-only

Retrieves the signed-in user's profile and mailbox status, including name, email, time zone, storage quota, and inbox/draft counts for account checks.

Instructions

Get the signed-in user's name, email address, time zone (Windows ID, used for times given without an offset), storage quota, and inbox/drafts counts.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context by listing the returned fields and explaining that the time zone is a Windows ID used for times given without an offset, which helps an agent interpret the result correctly.

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?

The description is a single, front-loaded sentence that lists the returned fields without filler. Every element earns its place by telling the agent what information will be available.

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?

There is no output schema, so the description carries the burden of explaining return values. It does so by enumerating the user's name, email address, time zone, storage quota, and inbox/drafts counts, which is complete for a simple mailbox-info tool.

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 has zero parameters, so the baseline is 4. The description does not need to explain parameter semantics, and it appropriately focuses on the returned information instead.

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 uses a specific verb, "Get," and a precise resource, the signed-in user's mailbox information, then enumerates the exact fields returned. It clearly distinguishes this from sibling tools that retrieve contacts, events, or messages by scoping the result to the signed-in user's own mailbox.

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?

The description implies when to use the tool by stating it retrieves the signed-in user's identity, time zone, quota, and counts, but it does not explicitly say when to choose this over alternatives or when not to use it. For a zero-parameter informational tool, the implied usage is adequate but not fully explicit.

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