Skip to main content
Glama
Sign In
EngageLab Agent Email MCP Server

EngageLab Agent Email MCP Server

Official
by Metaverse-Cloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_message

Retrieve full details of an inbound email message by its UID, including body content and attachments.

Instructions

Get full details of one inbound message by its UID, including body and attachments.

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": {
      "messageUid": "<messageUid>"
    },
    "name": "get_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageUidYesMessage UID from list_inbound_messages

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the safety profile. It indicates a read-only 'Get' operation and discloses the return scope (body and attachments), but it does not mention error behavior, auth, or any side effects. For a simple retrieval this is minimally sufficient.

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?

A single front-loaded sentence with no filler. 'Get full details... by its UID, including body and attachments' delivers purpose and return scope efficiently.

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?

With one required parameter and no output schema, the description covers the key return contents (body and attachments) and the input source. It omits only edge-case behavior like handling invalid or missing UIDs, which is minor for a low-complexity fetch tool.

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?

The input schema already documents messageUid fully with 100% coverage, including its source ('from list_inbound_messages'). The description adds only the 'by its UID' phrasing, which restates the schema, so the baseline of 3 applies.

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 states a specific verb (Get), resource (one inbound message), scope (by UID), and content (full details including body and attachments). It clearly distinguishes this from list_inbound_messages by focusing on a single message's full details.

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 parameter description 'Message UID from list_inbound_messages' implies the tool is used after listing messages, and the tool name contrasts with list/get_thread siblings. However, the description does not explicitly state when to choose this over get_thread or reply_email, leaving usage context implicit.

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