Skip to main content
Glama

Get the mailbox import status

get_mailbox_import_status
Read-only

Use this when a bulk mailbox import was started outside this conversation and the user asks whether it is still running. Returns whether the organization has an import connecting mailboxes right now, and when it started. Free. It does not say which mailboxes connected.

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_import_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds genuine value beyond them: it states the call is free and, importantly, discloses the limitation that per-mailbox detail is absent, which prevents the agent from over-interpreting the result. It stops short of describing the response shape in detail, which keeps it from a 5.

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?

Three short sentences, each doing distinct work: usage trigger, return contents, and known limitation. The most decision-relevant information (when to call) is front-loaded and there is no filler.

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 no-parameter, read-only status check with no output schema, the description supplies everything an agent needs: when to reach for it, what it returns at a high level, and what it deliberately omits. Complexity is low and the coverage matches it.

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 takes zero parameters, so the baseline is 4 and there is no parameter meaning the description could be expected to add. Nothing in the description conflicts with the empty 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 gives a specific verb and resource ('returns whether the organization has an import connecting mailboxes right now, and when it started') and explicitly bounds the scope with 'It does not say which mailboxes connected.' An agent can tell exactly what this tool reports and what it does not, without consulting any 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 when a bulk mailbox import was started outside this conversation and the user asks whether it is still running' is a concrete trigger condition that also implies the negative case (imports started in-conversation need no lookup). No named alternative is offered, but none of the listed siblings appears to be an import-status equivalent, so the guidance is clear rather than incomplete.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources