Skip to main content
Glama
Sign In

DiviMail

by tech.divindi
OverviewDiscussionsAdmin

divimail_read

Read-onlyIdempotent

Open and read one email in full (body and details) from your agent's mailbox. Call after divimail_inbox using a messageId from that list; then call divimail_mark_read if you want it marked read. When connected through an app sign-in, no token or address is needed.

Input Schema

NameRequiredDescriptionDefault
emailNoYour agent's full @divindi.io email address (e.g. myagent@divindi.io). Omit it when signed in: the connection already knows your address.
tokenNoOptional when signed in through an app. Otherwise a JWT from divimail_login, divimail_authenticate or divimail_service_token
messageIdYesMessage ID from divimail_inbox

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / email / description
      Previous value: -"Your agent's full @divindi.io email address (e.g. myagent@divindi.io)"New value: +"Your agent's full @divindi.io email address (e.g. myagent@divindi.io). Omit it when signed in: the connection already knows your address."
    • changedInput schema / properties / token / description
      Previous value: -"JWT token from divimail_login, divimail_authenticate or divimail_service_token"New value: +"Optional when signed in through an app. Otherwise a JWT from divimail_login, divimail_authenticate or divimail_service_token"
    • changedInput schema / required
      Previous value: -[
-  "email",
-  "messageId"
-]New value: +[
+  "messageId"
+]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds real value by saying the full body and details are returned and that app sign-in removes the credential burden, though it says nothing about how a missing or foreign messageId behaves or about pagination/size limits on large messages.

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, front-loaded with what the tool returns, followed by sequencing and auth notes. No filler or redundancy.

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 single-record fetch with full annotation coverage, the description is nearly sufficient. The gap is the return shape: 'body and details' hints at content but does not indicate whether attachments, headers, or HTML vs plain text are included, which matters since there is no output schema.

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%, so the schema already explains email, token and messageId in comparable detail; the description's 'messageId from that list' largely restates the schema. Baseline 3 is appropriate since the description adds no new syntax, format or validation detail for the parameters.

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?

States a specific verb and resource ('Open and read one email in full (body and details)') plus the source mailbox, which clearly separates it from divimail_inbox (listing) and divimail_mark_read (state change). An agent can select it without opening 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 Guidelines5/5

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

Gives an explicit workflow: call after divimail_inbox, pass a messageId from that list, then optionally call divimail_mark_read. It also names the auth condition under which token/address are unnecessary, so the prerequisites are spelled out rather than inferred.

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

All DiviMail toolsInspect
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