Skip to main content
Glama
hypr-tools

hypr-tools

by 0aaryan

set_notification_paused

Pause or unpause notification display by setting paused to true or false.

Instructions

Pause or unpause notification display

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": {
      "paused": "<paused>"
    },
    "name": "set_notification_paused"
  }
}

Input Schema

NameRequiredDescriptionDefault
pausedYestrue to pause, false to unpause

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is known. The description adds that the operation is a reversible pause of display rather than of history, but it does not say whether in-flight or queued notifications are affected, whether the state survives restarts, or how it relates to DND.

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 zero waste, pairing both directions of the toggle compactly. It is arguably too terse for a tool that overlaps a sibling, but nothing is redundant.

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?

For a one-boolean tool with annotations covering safety, the essentials are present. The notable gap is the absence of any routing versus toggle_dnd and get_dnd_status, which an agent needs when selecting among notification-suppression tools.

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 coverage is 100% and the single boolean's meaning ('true to pause, false to unpause') is fully documented in the schema. The description adds nothing beyond that, so baseline 3 applies.

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 (pause/unpause) and resource (notification display), so the agent knows exactly what changes. It does not, however, distinguish itself from the sibling toggle_dnd, which appears to control a closely related behavior.

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

Usage Guidelines2/5

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

There is no guidance on when to pause notifications versus using toggle_dnd, nor whether the state persists or interacts with DND. The agent must infer the choice between two notification-suppression tools from names alone.

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

Deploy Server

Other Tools