Skip to main content
Glama

graph_get_mail_tips

Retrieve mail tips for recipient email addresses to check out-of-office replies, mailbox-full status, and recipient scope before sending messages. Supports shared mailboxes and selectable tip types.

Instructions

Get mail tips for recipients. Use this to check whether someone is out of office.

Args: email_addresses: Recipient addresses to look up. options: Mail tips to request (default "automaticReplies", "mailboxFullStatus", "recipientScope"). Other values: customMailTip, deliveryRestriction, externalMemberCount, maxMessageSize, moderationStatus, totalMemberCount. mailbox: Shared mailbox address or user ID to act on. Empty targets your own mailbox. Requires the delegated Mail.*.Shared permissions.

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_addresses": "<email_addresses>"
    },
    "name": "graph_get_mail_tips"
  }
}

Input Schema

NameRequiredDescriptionDefault
mailboxNo
optionsNo
email_addressesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A4.3/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose a genuinely useful behavioral fact — the shared-mailbox path requires delegated Mail.*.Shared permissions and an empty value targets your own mailbox — but it says nothing about return shape, whether unavailable tips are omitted or error out, or any throttling behavior.

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?

Purpose and the headline use case are front-loaded in two short sentences, then per-argument detail follows in an Args block. Every line adds information; there is no filler or restated name.

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 three-parameter read tool with no output schema and no annotations, the definition covers purpose, every parameter, defaults, and the permission prerequisite. The main remaining gap is what the response contains (e.g., whether each requested tip is always present), which an agent would have to discover by calling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, yet the description documents all three parameters: the recipient list, the mailbox targeting semantics with its permission requirement, and the options array with its default set plus the full list of additional accepted values. That enumeration is information the schema does not contain (no enums), so the description fully compensates for the coverage gap.

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 first sentence names a specific verb and resource ("Get mail tips for recipients") and the second adds a concrete primary use case (out-of-office checks). Mail tips is a distinct Graph resource, so an agent can distinguish this from the mail-reading and mail-sending siblings without opening the schema.

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?

"Use this to check whether someone is out of office" gives a clear triggering scenario for the most common case. It does not state when not to use it or name an alternative sibling, but the context it provides is unambiguous.

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