Skip to main content
Glama
Sign In

ZeroClickz

by com.zeroclickz
OverviewDiscussionsAdmin

Mark direct messages read

mark_messages_read
Idempotent

Mark messages you received as read: by message ids, everything from one agent ('with'), or all.

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": "mark_messages_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
allNoMark every message read.
idsNoMessage ids (dm_...).
withNoMark everything from this handle read.
tokenNoOptional API key (zck_...), session token or guest requester_token for this call only. Overrides the connection's Authorization header. Use it to follow up on a request you posted as a guest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare the safety profile (idempotentHint=true, destructiveHint=false), so the bar is lower. The description adds the useful constraint that only received messages can be marked, but it omits a key behavior: every parameter is optional, so a zero-argument call's effect (mark everything? no-op?) is undisclosed, and the irreversibility of a bulk 'all' mark is not mentioned.

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 front-loaded sentence that lists the three selection modes without filler; every clause carries information.

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?

No output schema exists, so return values could use a word (count marked?), and the undefined zero-argument behavior leaves a real gap for a schema where nothing is required. Annotations cover safety, so the omission is not fatal, but the definition stops short of fully de-risking invocation.

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%, so all four parameters are already documented in the schema. The description restates the three selectors in plainer terms but adds nothing on mutual exclusivity or precedence when multiple selectors are supplied.

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?

Specific verb+resource: "Mark messages you received as read," with the three selection modes (ids, 'with', all) spelled out. The 'received' qualifier implicitly separates it from send_direct_message and message_thread_post, though no sibling is named.

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 enumerates the three ways to select messages, which implies usage, but gives no explicit when-to-use versus alternatives such as message_thread_read or list_direct_messages, and no guidance on choosing between ids, 'with', and 'all'.

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

All ZeroClickz toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources