Skip to main content
Glama
Sign In
homebutler

homebutler

by Higangssh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

notify_test

Sends one real test notification through every configured channel and reports which channels received it, helping verify delivery paths.

Instructions

Send one test notification through every configured channel and report which ones arrived. A real message goes out to each, so anyone reading those channels sees it

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

Input Schema

NameRequiredDescriptionDefault
serverNoRemote server name from config (optional, runs locally if omitted)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.35.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the bar is lower, yet the description adds the crucial side effect that a real message is delivered to each channel and visible to channel readers. That is exactly the kind of non-obvious consequence an agent needs before invoking. It stops short of mentioning throttling, duplicate sends, or what happens when a channel fails.

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, zero filler, with the action and its scope front-loaded and the warning about real message delivery immediately following.

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?

No output schema exists, and the description indicates the return content ('report which ones arrived'), plus discloses the external side effect. For a zero-required-parameter tool this is nearly complete, missing only failure-mode or prerequisite detail.

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 100% for the single optional 'server' parameter, so the schema already carries the semantics. The description adds nothing about the server-vs-local behavior, leaving the schema to do all the work; 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?

Specific verb and resource: sends a test notification through every configured channel and reports delivery results. The word 'test' distinguishes it from the real alerting siblings (alerts, watch_add), though no sibling is named explicitly.

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 purpose implies the use case (verifying that notification channels are working), but the description never states when to prefer this over doctor or alerts, nor any exclusions or prerequisites such as requiring channels to be configured first.

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