Skip to main content
Glama

Coline

List mailboxes

list_mailboxes
Read-onlyIdempotent

Lists the mail accounts the person can read (their @coline.email inbox, Gmail, shared and custom-domain inboxes) and the addresses they can send from. Use it before sending when they have more than one.

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": {
      "workspace": "<workspace>"
    },
    "name": "list_mailboxes"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
sendAsYes
accountsYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and idempotence are fully covered structurally. The description adds value by clarifying the exact result set (readable accounts plus sendable addresses), which goes beyond the annotations. However, it says nothing about ordering, volume, or how shared versus personal mailboxes are distinguished in the response, and it defers all return-shape detail to the output schema.

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?

Two short sentences: the first defines the result set, the second gives the trigger. The purpose is front-loaded and there is no filler, hedging, or repetition of the title.

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 single-parameter, read-only list tool with an output schema and rich annotations, this covers what matters: what is returned and when to call it. The only minor gap is the absence of any hint about ordering or scope of results when the person has many mailboxes, which the output schema presumably handles.

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 description coverage is 100% and there is a single required parameter (workspace) whose description already explains it is a slug from workspaces.list with a concrete example. The tool description never mentions the workspace argument, so it adds no meaning beyond the schema; the baseline of 3 applies.

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?

Names a specific verb and resource ("Lists the mail accounts") and enumerates the concrete scope it returns: the person's @coline.email inbox, Gmail, shared and custom-domain inboxes, plus send-from addresses. That is much more specific than a bare 'list mailboxes', though it does not explicitly contrast itself with the nearby list_mail_threads or list_channels siblings.

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?

Gives a concrete trigger condition: use it before sending when the person has more than one mailbox. That is real when-to-use guidance rather than a restatement of purpose. It stops short of explicit exclusions or naming an alternative tool for the single-mailbox case, so it does not reach the top band.

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