Skip to main content
Glama

email_channel_read

Read-onlyIdempotent

Read the email channel setup of the workspace: sending domains (with the DNS records to add and their verification state), inboxes (addresses agents answer) and recent email events. Actions: domains — sending domains | inboxes — inboxes and their assigned agent | recent_events — recent inbound / outbound email events

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": {
      "action": "<action>"
    },
    "name": "email_channel_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNocompact (default) = light mode: long text is cut and bulky blobs are replaced by a size marker. full = complete API response.
limitNoFor recent_events: max 100.
orgIdNoOptional organization scope.
actionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior; the description adds useful return context: DNS records and verification state for domains, agent-assigned inboxes, and inbound/outbound recent events. It still leaves some behavioral gaps, such as the recent-events time window and output detail, but does not contradict annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loads the tool purpose, and then maps actions tersely. There is little waste, though the action list slightly repeats 'sending domains' from the opening sentence.

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 read-only tool with no output schema, the description explains the main data families returned and includes useful details like DNS verification state and agent inbox assignment. It omits some depth, such as recent-event time range and event fields, but the schema covers parameter mechanics, so it is largely complete for selection.

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 schema documents mode, limit, and orgId at 75% coverage, while the description supplies the otherwise undocumented semantic meaning for each action enum value. It does not elaborate much on mode or limit beyond the schema, but the action semantics add clear value.

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?

States a specific verb ('Read') and resource ('email channel setup of the workspace'), then enumerates domains, inboxes, and recent email events. It is clearly a read operation, though it does not explicitly contrast with email_channel_write or other channel-reading siblings, so sibling differentiation is only implied by the name and annotations.

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 action breakdown implies which action to use for domains, inboxes, or recent events, giving practical routing within the tool. However, it gives no explicit when-to-use guidance against write or other channel-reading siblings, and states no prerequisites or exclusions.

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