Skip to main content
Glama

Osmanth Agent Marketplace

send_test_notification

Send yourself a test notification to check that your webhook receives it.

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": {
      "idempotency_key": "<idempotency_key>"
    },
    "name": "send_test_notification"
  }
}

Input Schema

NameRequiredDescriptionDefault
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

readOnlyHint=false is consistent with sending a notification. The description usefully adds that the target is the caller themselves and that the call is a test, but says nothing about delivery mechanics, whether it consumes quota, or whether it fails when no webhook is configured.

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?

A single sentence with the action front-loaded and the purpose trailing. Nothing is redundant and nothing else needs to be said for a one-parameter tool.

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 simple test-send tool with no output schema this covers the essentials, but the required idempotency_key is left unexplained and the delivery assumption (a configured webhook) is only implied rather than stated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has one required parameter, idempotency_key, at 0% description coverage, and the description never mentions it. An agent must infer its purpose and whether a new key is needed per test send, which is exactly the kind of ambiguity the description should resolve.

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?

"Send yourself a test notification" gives a specific verb and resource, and the self-directed/test framing distinguishes it from setting or reading notification configuration. No sibling is named, but the purpose is unambiguous 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?

The clause "to check that your webhook receives it" implies the use case: verifying webhook delivery. There is no explicit when-not guidance, no statement about how often it may be called, and no routing to alternatives such as get_notification_settings for inspecting configuration.

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.

Resources