Narrareach

List draft comment notifications

list_draft_comment_notifications

Read-onlyIdempotent

Find the writer's own drafts that have comments they have not read yet, newest first, with each draft's unread count and its latest unread comments (excerpted to 280 characters). Unread means written by someone else after the writer last opened that draft's comments in Narrareach. Drafts whose comment notifications the writer muted are left out unless includeMuted is true. Read-only: it does not mark anything read. Use list_draft_comments with a draftId for the full threads.

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

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum drafts to return.
`includeMuted`	No

Output Schema

Name	Required	Description	Default
`drafts`	Yes
`hasMore`	Yes
`totalDrafts`	Yes
`connectedAccount`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is structured; the description still earns credit by explicitly reassuring 'it does not mark anything read' and by defining 'unread' in terms of Narrareach's last-opened semantics. It doesn't cover rate limits or pagination beyond newest-first ordering.

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?

Four sentences, front-loaded with what the tool returns, then exclusions, then the read-only caveat, then the sibling redirect. No redundant restatement of the title or annotations.

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?

An output schema exists, so return-value explanation isn't required, yet the description still summarizes the return (unread count plus latest unread comments excerpted to 280 chars). Combined with zero required params and the muted/unread semantics, an agent has everything needed to call this correctly.

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

Parameters4/5

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

Schema coverage is 50%: limit is documented in-schema, but includeMuted is bare there and the description compensates by explaining that muted drafts are excluded unless includeMuted is true. No added detail on the limit's max of 50 or on what the newest-first ordering means for paging, so not a 5.

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 ('Find the writer's own drafts that have comments they have not read yet') plus ordering, return shape, and exclusions. Explicitly routes to the sibling list_draft_comments for full threads, so it's distinguishable from list_draft_comments and list_drafts.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit alternative ('Use list_draft_comments with a draftId for the full threads') and a condition that selects it. Also states the muted-draft behavior and the includeMuted escape hatch, so the agent knows when results will be suppressed.

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

All Narrareach tools Inspect

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

Need Help?