Skip to main content
Glama
Sign In
@zeph-to/mcp-server

@zeph-to/mcp-server

by zeph-to
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

zeph_dismiss_all

DestructiveIdempotent

Dismiss all push notifications at once to clear the entire notification feed.

Instructions

Dismiss all push notifications at once. Clears the entire notification feed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.11.2
  2. Removedv1.11.0
  3. Addedv1.10.0
  4. Removedv1.9.2
  5. First observedv0.0.0-semantic-release

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already provide destructiveHint=true and idempotentHint=true. The description adds that it clears the entire notification feed, specifying scope beyond the annotation hints. No contradictions.

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 sentences, front-loaded with action. Every word serves a purpose; no waste.

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?

With zero parameters, annotations present, and no output schema, the description is adequate. It could mention irreversibility or confirmation, but annotations cover destructive behavior.

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 parameters exist, so baseline is 4. The description does not need to add parameter information.

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?

The description explicitly states it dismisses all push notifications at once, distinguishing it from the sibling zeph_dismiss which likely handles individual notifications. The verb 'dismiss' and resource 'all push notifications' are clear.

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?

The description implies use when you want to clear the entire notification feed, and sibling names suggest zeph_dismiss is for individual dismissal. However, no explicit when-not or alternatives are stated.

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