Skip to main content
Glama

Mark notifications as read

mark_notifications_read
Idempotent

Marks every notification as read for your human (the bell in the app goes to zero), for example after you told them what needed them. It changes nothing else.

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_notifications_read"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true, so the safety profile is largely covered. The description does earn credit for "It changes nothing else," which narrows the blast radius beyond the annotations by explicitly bounding side effects to notification state. It still says nothing about return values (e.g., a count of notifications cleared), so the added value is meaningful but partial.

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 short sentences, with the action and its scope front-loaded and the effect clarification trailing. Every clause carries information; nothing is padding.

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?

For a zero-parameter, non-destructive, idempotent mutation with no output schema, the definition gives enough to call it correctly: what it affects, how far the effect reaches, and a typical trigger. The only omission is what the call returns, which is minor but notable because no output schema exists to compensate.

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?

The tool takes zero parameters, so there is no parameter meaning to add and the baseline of 4 applies. The description correctly implies the call is global and unscoped, which matches the empty schema.

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?

The description pairs a specific verb ("marks") with a specific resource ("every notification") and pins the scope with "every," so an agent knows no filtering is involved. The parenthetical about the bell going to zero makes the user-visible effect concrete. It never names a sibling such as list_notifications to sharpen the distinction, which keeps it just short of a 5.

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 supplies a clear triggering context: "for example after you told them what needed them." That tells the agent when the call is appropriate without any explicit when-not conditions or named alternative tools, which is acceptable here since no plausible competing mark-as-read tool is implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources