Skip to main content
Glama
owlpost

owlpost

mark_read

Idempotent

Set or clear a message's Seen flag to mark it read or unread in a specified account, folder, and UID.

Instructions

Mark a message as read or unread by setting or clearing its \Seen flag.

Args: account: Account name from list_accounts. folder: Folder containing the message. uid: Message UID. read: True to mark read (default), false to mark unread.

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": {
      "account": "<account>",
      "folder": "<folder>",
      "uid": "<uid>"
    },
    "name": "mark_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidYes
readNo
folderYes
accountYes

Output Schema

NameRequiredDescriptionDefault
uidYes
seenYes
folderYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "folder": {
      +      "title": "Folder",
      +      "type": "string"
      +    },
      +    "seen": {
      +      "title": "Seen",
      +      "type": "boolean"
      +    },
      +    "uid": {
      +      "title": "Uid",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "uid",
      +    "folder",
      +    "seen"
      +  ],
      +  "title": "ReadState",
      +  "type": "object"
      +}
  2. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value by disclosing that the operation is a \Seen flag toggle rather than a content change, but says nothing about permission requirements, server sync, or what happens on an invalid uid.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose sentence is front-loaded and the Args block is a compact, scannable list. Some redundancy with the schema exists, but given 0% schema coverage that repetition 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?

An output schema exists, so return values need not be explained, and the tool is simple. Still missing are the call-chain guidance (resolve_folder for the folder path, search_messages for the uid) and the behavior when the UID does not exist, which matter for a four-parameter mutation.

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 0%, so the description carries the full burden, and it does enumerate all four parameters including the default for read. However, the semantics are thin: "uid: Message UID" is essentially a restatement of the name and does not explain where a uid comes from (search_messages) or whether it is folder-scoped.

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+resource (mark a message as read or unread) and even names the underlying mechanism, the \Seen flag. It is distinguishable from the closest sibling, flag_message, only by inference from the flag name; nothing explicitly contrasts the two.

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 Args block hints at provenance for account ("from list_accounts") and folder, which implies a discovery workflow, but there is no explicit when-to-use guidance, no exclusion versus flag_message, and no statement of prerequisites for obtaining a valid uid.

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