fmsg-mcp

Mark fmsg messages read

mark_read

Idempotent

Marks specified received messages as read, including reaction messages, and clears their unread indicator; reading a message does not mark it read.

Instructions

Mark received messages as read, including reaction messages listed with include_reactions. Reading a message with get_message does not mark it read. Marking a message read clears an indicator you set on it.

Input Schema

Name	Required	Description	Default
`ids`	Yes	ids of the messages to mark read (up to 100)

Output Schema

Name	Required	Description	Default
`failed`	Yes
`marked`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv1.1.0Oct 15, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / ids / description
```
Added value: +"ids of the messages to mark read (up to 100)"
```
- changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +{}
```
- changedOutput schema / properties / failed / items / additionalProperties
```
Previous value: -falseNew value: +{}
```
- changedOutput schema / properties / marked / items / additionalProperties
```
Previous value: -falseNew value: +{}
```
First observedv0.1.3Sep 5, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The annotations already declare non-read-only, idempotent, non-destructive, and closed-world behavior. The description adds useful behavioral context: get_message does not mark messages read, and marking read clears an indicator set on the message.

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?

The description is three short sentences, front-loaded with the core action and followed by relevant behavioral clarifications. There is no wasted wording.

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

Completeness5/5

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

Given the simple one-parameter schema, full parameter coverage, annotations, and an output schema, the description provides enough context for correct invocation. It covers the key side effect and the important distinction from get_message.

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 ids parameter is fully documented in the schema, including the 100-item limit. The description does not add parameter-specific meaning beyond the schema, so the 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 states a specific verb and resource: marking received messages as read. It also distinguishes this from get_message by explicitly noting that reading a message does not mark it read.

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?

It gives clear context for using this tool instead of get_message when read state must change, and it mentions reaction messages listed with include_reactions. It does not explicitly describe when not to use it or other alternatives, but the usage context is clear.

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

Deploy Server