Skip to main content
Glama
Sign In
magents

magents

by abnegate
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

ack

Mark a specified email as read by mail id, or mark all current emails as read when no id is provided.

Instructions

Mark inbox mail as read through a mail_id (or all current mail).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ack"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentNo
throughNoMail id to ack through; omit to ack all current mail
session_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.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 the burden of behavioral disclosure. It clearly states the mutating action (mark as read), but does not explain the exact semantics of 'through' (specific message vs up-to-and-including), idempotency, or any side effects beyond marking read.

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 sentence with no filler, and the scoping alternative '(or all current mail)' is front-loaded and clearly separated. It is appropriately compact for a simple mail action.

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

Completeness2/5

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

Given three parameters, no annotations, and no output schema, the description is too sparse. It leaves agent and session_id unexplained, and does not clarify the return value or the precise behavior when a mail_id is supplied versus omitted. This is insufficient for an agent to call the tool correctly in all cases.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%, and the description does not compensate for the undocumented 'agent' and 'session_id' parameters. It essentially restates the 'through' behavior already present in the schema, adding no new meaning for the remaining 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?

The description uses a specific verb+resource ('Mark inbox mail as read') and clearly distinguishes this tool from siblings like inbox, reply, send_message, and await_reply. The mail_id/all-current-mail scoping further clarifies what it operates on.

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 description conveys the core operation and the two modes (specific mail_id vs all current mail), but does not explicitly state when to choose this over alternatives or mention any exclusions. Usage context is implied rather than explicitly guided.

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