Ranla

Get received email

get_received_email

Read-only

Get one inbound email, including its headers and body.

Input Schema

Name	Required	Description	Default
`id`	Yes	Received email id

Output Schema

Name	Required	Description	Default
`received_email`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 14, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "received_email": {
+      "properties": {
+        "attachment_count": {
+          "type": "number"
+        },
+        "attachments": {
+          "items": {
+            "properties": {
+              "content_id": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "content_type": {
+                "type": "string"
+              },
+              "data": {
+                "description": "Base64 content, when included",
+                "type": "string"
+              },
+              "filename": {
+                "type": "string"
+              },
+              "size": {
+                "description": "Bytes",
+                "type": "number"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "auto_submitted": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "bounced": {
+          "type": "boolean"
+        },
+        "cc": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "created_at": {
+          "description": "ISO 8601",
+          "type": "string"
+        },
+        "domain_id": {
+          "type": "string"
+        },
+        "domain_name": {
+          "type": "string"
+        },
+        "from": {
+          "type": "string"
+        },
+        "html_body": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "id": {
+          "description": "Received email id",
+          "type": "string"
+        },
+        "in_reply_to": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "mail_from": {
+          "description": "Envelope sender",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "message_id": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "rcpt_to": {
+          "description": "Address it was delivered to",
+          "type": "string"
+        },
+        "received_at": {
+          "description": "ISO 8601",
+          "type": "string"
+        },
+        "received_with_ssl": {
+          "type": [
+            "boolean",
+            "null"
+          ]
+        },
+        "references": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "spam_status": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "status": {
+          "type": "string"
+        },
+        "subject": {
+          "type": "string"
+        },
+        "text_body": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "to": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "id"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "received_email"
+  ],
+  "type": "object"
+}

First observedOct 14, 2026

TDQS

B3.4/5.0

Behavior3/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 safety is covered. The description adds only the return content (headers and body), not pagination, body format, or error behavior for an unknown id; with annotations carrying the profile this is a modest addition.

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?

One short sentence, front-loaded with the verb and resource, and the payload clause adds information rather than padding. No waste.

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 an output schema present, the description need not describe return structure, and the annotations cover the safety profile. What remains thin is routing context – nothing says when to choose this over get_email or list_received_emails – but for a simple one-param read the description is nearly sufficient.

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 the single 'id' parameter is documented as 'Received email id'. The description adds no syntax, format, or source guidance beyond the schema, so the baseline 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?

States a specific verb and resource ('Get one inbound email') and enumerates the payload ('headers and body'), which tells the agent what comes back. It does not differentiate itself from the sibling get_email, leaving the inbound-vs-outbound distinction implicit in the word 'received' rather than explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance, no prerequisites, and no mention of alternatives such as list_received_emails or get_email. The agent must infer from the name alone that this is the single-item lookup counterpart to the list tool.

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

All Ranla tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?