Skip to main content
Glama
meshive-mcp

meshive-mcp

Official
by meshive

Mark Host Messages Read

mark_host_messages_read
Idempotent

Marks incoming messages for a hosted machine as read, updating only that host's unread count without confirmation; provide the machine ID and valid incoming message IDs.

Instructions

Mark incoming messages of a hosted machine read, like opening them in the console; it changes only the host's own unread count, so it needs no confirmation. machine is the machine_id, and message_ids are message id values from host_messages for that machine (direction "in"). An id that isn't a message of this machine is refused (not_found) and nothing is marked. Every write requires operation_id. Reuse the ID returned by the preview, or generate a UUID before the first call. Keep it for confirmation and all retries; a new ID means a new operation. After a timeout, check operation_status and resource state before retrying.

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": {
      "machine": "<machine>",
      "message_ids": "<message_ids>"
    },
    "name": "mark_host_messages_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
machineYes
message_idsYes
operation_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.10.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations it discloses that the write is low-impact (only the host's unread count, no confirmation needed), that an invalid id causes an all-or-nothing refusal (not_found, nothing is marked), and the full operation_id lifecycle including reuse on retries. This is exactly the context the readOnlyHint=false / idempotentHint=true annotations cannot convey.

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 core behavior and constraints are front-loaded in the first sentence, with operation_id guidance following. The second paragraph is generic cross-tool boilerplate that adds length but is still actionable for this mutation, so only minor trimming is warranted.

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?

For a 3-parameter mutation with an output schema, the definition covers inputs, atomicity on failure, side-effect scope, and retry/idempotency handling. Nothing an agent needs to call it safely is absent, and return values are left to the output schema.

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

Parameters5/5

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

Schema coverage is 0%, so the description carries the burden and does: 'machine' is identified as the machine_id, 'message_ids' as id values from host_messages filtered to direction 'in', and 'operation_id' is explained in depth (reuse the preview's ID or generate a UUID before the first call, keep it for all retries).

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 and resource ('Mark incoming messages of a hosted machine read') and immediately clarifies the real-world semantics ('like opening them in the console'). It also scopes the effect ('changes only the host's own unread count'), which distinguishes it from siblings like send_host_message or host_messages.

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?

Names where the inputs come from ('id values from host_messages for that machine (direction "in")') and prescribes a retry protocol via operation_status after a timeout. What's missing is an explicit exclusion or when-not-to-use statement, so it lands just short of the top mark.

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