Skip to main content
Glama
Sign In
Suzu (鈴) - Claude Code Notification Server

Suzu (鈴) - Claude Code Notification Server

by denar90
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

question_alert

Receive alerts when Claude requires additional information or clarification during interactions, enabling timely responses to follow-up questions.

Instructions

Alert the user when Claude is asking additional questions or needs clarification

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

Input Schema

NameRequiredDescriptionDefault
questionNoThe question or clarification Claude is askingClaude has a question
contextNoBrief context about what Claude needs help withAdditional information needed

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While it states the tool 'alerts the user,' it doesn't specify how this alert manifests (visual notification, sound, etc.), whether it's interruptive, what permissions might be required, or any rate limits. The description is too vague about the actual behavior beyond the basic purpose.

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?

The description is a single, efficient sentence that gets straight to the point. There's no wasted language or unnecessary elaboration. It's appropriately sized for a simple alert tool and front-loads the essential information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that this is an alert/notification tool with no annotations and no output schema, the description is insufficient. It doesn't explain what the alert looks like, how it's delivered, what happens after the alert, or any error conditions. For a tool that presumably interacts with the user interface, more behavioral context is needed.

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?

The input schema has 100% description coverage, with both parameters ('question' and 'context') clearly documented in the schema itself. The description adds no additional parameter information beyond what's already in the schema. According to the scoring rules, when schema_description_coverage is high (>80%), the baseline is 3 even with no param info in the description.

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 clearly states the tool's purpose: 'Alert the user when Claude is asking additional questions or needs clarification.' This specifies the verb ('alert') and the trigger condition (Claude asking questions/needing clarification). However, it doesn't differentiate this tool from the sibling 'notify' tool, which appears to be a more general notification tool.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention the sibling 'notify' tool or explain why one would choose this specific alert tool over a general notification mechanism. There's no information about prerequisites, timing considerations, or exclusions.

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