Skip to main content
Glama
Sign In

DiviMail

by tech.divindi
OverviewDiscussionsAdmin

divimail_mark_read

Idempotent

Mark an email in your agent's inbox as read so it is not handled twice. Use after divimail_read (or divimail_inbox) with the same messageId. 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/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true, destructiveHint=false and readOnlyHint=false, so the safety profile is covered. The description adds genuinely new behavioral context the annotations do not carry: the auth model ('When connected through an app sign-in, no token or address is needed') and the state-management intent of avoiding duplicate handling.

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 sentences, front-loaded with the action and its rationale, then the prerequisite call, then the auth shortcut. Every clause carries information an agent needs before invoking the tool.

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 three-parameter, one-required mutation with no output schema, the description covers purpose, ordering, identifier consistency and auth. The only gap is error/edge behavior (what happens if the message is already read or the ID is unknown), which is partly mitigated by idempotentHint=true.

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 email, token and messageId are all documented in the schema, including the 'omit when signed in' behavior. The description only adds the constraint that messageId must match the one used in the preceding read/inbox call, which is a small increment over the schema's 'Message ID from divimail_inbox'.

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 ('Mark an email in your agent's inbox as read') plus the reason ('so it is not handled twice'). The sibling set contains no other mark-state tool, so the purpose is unambiguous, though it never explicitly says what it is not (e.g., it does not mark unread or delete).

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 explicit sequencing: 'Use after divimail_read (or divimail_inbox) with the same messageId', naming the two sibling tools that produce the required identifier. It lacks a when-not-to-use clause (e.g., already-read messages or messages not in the inbox), which keeps it short of a 5.

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