Skip to main content
Glama

TesterSwap

Mark notifications read

mark_notifications_read
Idempotent

Mark specified notifications, or all your notifications, as read.

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
mark_all_readNo
notification_idsNo

Output Schema

NameRequiredDescriptionDefault
marked_countYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare idempotentHint=true, destructiveHint=false and readOnlyHint=false, so the safety profile is covered by structured data. The description adds nothing beyond that: it never states what happens in the ambiguous case where neither parameter is supplied (both are optional, zero required), whether the call is idempotent, or that at most 100 IDs are accepted.

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 compact sentence with the primary action front-loaded and the two modes stated inline. No filler; only fault is that no room is left for the edge cases noted above.

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?

The tool is simple and an output schema exists, so return values need not be explained. Still, with both parameters optional and no required field, the description should clarify the default/empty-payload behavior and mutual exclusivity of the two modes; that gap matters for correct 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 0%, so the description must carry the load: it does explain that the two modes are 'specified notifications' versus 'all your notifications', which maps meaningfully onto notification_ids and mark_all_read. However it never states that the modes are mutually exclusive, what an empty request does, or the 100-item cap, so the compensation is partial.

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 gives a specific verb ('mark ... as read') and resource ('notifications'), plus the two supported scopes. An agent can distinguish it from read-only siblings like list_notifications without opening the schema.

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?

Usage is implied by the verb — call it when notifications should become read — and the two modes are named. There is no explicit when-not guidance, no statement about prerequisites or side effects, and no routing to a sibling, so it stays at implied usage.

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.