Skip to main content
Glama
Sign In
mail-macos-mcp

mail-macos-mcp

by Maxtechexplore
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Marquer lu / non lu

marquer_mail

Mark an email as read or unread using its unique identifier. Manage email read status directly from your desktop.

Instructions

Marque un mail comme lu ou non lu, à partir de son identifiant.

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": {
      "id": "<id>",
      "lu": "<lu>"
    },
    "name": "marquer_mail"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesIdentifiant du mail
luYestrue = marquer comme lu, false = marquer comme non lu

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses the core behavior (toggle read/unread) but omits any side effects, permissions, or idempotency details. For a simple toggle, this is acceptable but not exemplary.

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, concise sentence that efficiently conveys the tool's purpose without unnecessary detail. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the low complexity of the tool and the absence of an output schema, the description is adequate. However, it does not specify the return value or confirm success/failure behavior, which would enhance completeness.

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 input schema already defines both parameters ('id' as mail identifier, 'lu' as boolean flag). The description adds no additional meaning beyond what the schema provides, so a baseline score of 3 is appropriate.

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 clearly states the tool's action: marking an email as read or unread using its identifier. It uses a specific verb+resource combination and distinguishes the tool from siblings like 'lire_mail' (reading) and 'corbeille_mail' (trashing).

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., moving, deleting, or sending). There is no mention of prerequisites or exclusion criteria, leaving the agent without context for selection.

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