fmsg-mcp

Mark fmsg messages read

mark_read

Idempotent

Marks up to 100 received messages as read, including reaction messages when include_reactions is used. Use after reading a message, since get_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.

Input Schema

TableJSON Schema

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

Output Schema

TableJSON 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/5.0

Behavior3/5

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

Annotations already declare the state-changing, idempotent, non-destructive profile, so the bar is lower. The description adds useful scope detail ('including reaction messages listed with include_reactions'), clarifying what actually gets marked, but says nothing about permissions or failure behavior.

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 tight sentences, purpose front-loaded, with the get_message caveat as a natural follow-up. No filler.

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?

Output schema and annotations are present, so return values and safety profile need not be restated. The description covers purpose, scope, and the key caveat; only permission/prerequisite details are absent, which is a minor gap.

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 single ids parameter is fully documented with type, pattern, and maxItems. The description adds no syntax or format detail beyond the schema, so baseline 3 applies.

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?

States a specific verb+resource ('Mark received messages as read') and explicitly distinguishes its effect from the sibling get_message, which does not mark messages read. An agent can tell what this does and how it differs from reading.

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?

Provides clear usage context by noting that reading via get_message does not mark a message read, implying this tool is required when read state must change. It does not, however, state exclusions such as whether it applies to sent messages or drafts.

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

Deploy Server