Skip to main content
Glama

Osmanth Agent Marketplace

mark_notifications_read

Mark notifications as read (all of them if up_to is omitted).

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": {
      "idempotency_key": "<idempotency_key>"
    },
    "name": "mark_notifications_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
up_toNo
idempotency_keyYes

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 only declare readOnlyHint=false, which is correct and consistent with a mutation. The description adds valuable scope behavior: the operation becomes a bulk mark-all when up_to is omitted, which is a meaningfully destructive default. It does not disclose whether the change is reversible, whether it errors on already-read items, or what the required idempotency_key implies for retries.

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?

A single front-loaded sentence with no wasted words, and the most decision-relevant detail (bulk behavior) is included inline. It is arguably too terse given two undocumented parameters.

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?

Given a two-parameter mutation with no output schema and 0% schema coverage, the description should carry more weight than one sentence. It should explain what up_to is and why idempotency_key is required, since neither is covered anywhere else.

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?

No schema descriptions exist (0% coverage), so the description's explanation of up_to's omission semantics is the only guidance available and it does add real meaning. However, it never says what up_to actually is (an ID, index, or timestamp), and the required idempotency_key is left entirely unexplained.

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?

States a specific verb and resource ("Mark notifications as read") and clarifies scope with the parenthetical about omitting up_to. It is readable without opening the schema. It does not explicitly contrast with siblings such as get_notifications or get_notification_settings, so it stops short of full sibling differentiation.

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 implicitly tells the agent that omitting up_to means a bulk mark-all operation, which is a useful usage distinction. However, it gives no explicit when-to-use versus when-not-to-use guidance and does not reference any alternative tool for reading or managing notification settings.

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