Skip to main content
Glama
Sign In

tlly

by dev.tlly
OverviewDiscussionsAdmin

Set alert webhook URL

set_alert_webhook
DestructiveIdempotent

Set or clear the workspace webhook URL for job-failure and dashboard status alerts (pass an empty url to clear). When events fire, tlly POSTs JSON to that URL (Slack and Discord incoming webhooks get a short text payload instead). Events include job_failed, status_changed (keep panel "id" fields in specs so alerts stay attached), and threshold_crossed. Email alerts work without a webhook. Caps: 12 emails and 60 webhooks per account per hour; the same panel is not alerted twice within an hour.

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

Input Schema

NameRequiredDescriptionDefault
urlNohttps URL, or empty to clear

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing what is actually sent (JSON POST, with a shortened text payload for Slack/Discord incoming webhooks), which events trigger it, and concrete rate limits (12 emails / 60 webhooks per account per hour) plus the one-hour per-panel dedup window. The destructiveHint=true annotation is consistent with the documented clear-by-empty-url behavior.

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?

Front-loaded with the action and scope, then layered with payload, events, and caps in a single dense paragraph. Every sentence carries information, though the parenthetical about keeping panel "id" fields is slightly buried mid-sentence rather than given its own line.

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

Completeness5/5

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

For a one-parameter, no-output-schema tool with annotations already covering safety and idempotency, the description supplies the missing operational context: trigger events, payload format, and throttling. An agent has everything needed to invoke it correctly and predict side effects.

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?

Schema coverage is 100% and the single parameter already documents "https URL, or empty to clear," so the baseline is 3. The description adds real meaning by explaining what the URL receives and how payload shape varies by destination, which helps the agent pick a valid endpoint.

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?

States a specific verb pair (set/clear) plus the exact resource (workspace webhook URL) and its scope (job-failure and dashboard status alerts). This cleanly separates it from the sibling per-target alert tools set_panel_alert and set_stale_alert, which an agent could otherwise confuse it with.

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?

Gives a concrete clearing instruction ("pass an empty url to clear") and a when-not signal ("Email alerts work without a webhook"), so the agent knows this is optional configuration. It never explicitly names the sibling alert tools as the alternative for per-panel or staleness alerting, leaving that routing to inference.

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

All tlly toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources