Skip to main content
Glama
Sign In

tlly

by dev.tlly
OverviewDiscussionsAdmin

Configure stale-data alerts

set_stale_alert
DestructiveIdempotent

Configure when tlly sends stale-data alert email and webhooks because a series stopped updating. after: auto (from the job schedule and point spacing, at least two days), off, hours, or a window like 48h or 7d. Use dashboard_id for every series on a dashboard, series for one series, or both for one series on one dashboard. One email and one webhook when it goes quiet; another when a newer point arrives. Counts toward the hourly caps.

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_stale_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNoauto, off, 48h, 7d, or a number of hours
seriesNooptional series name
dashboard_idNooptional dashboard id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint/readOnly=false, so the description's added value is behavioral: one email and one webhook on going quiet plus another on recovery, and consumption of hourly notification caps. It does not explain what a re-configure destroys (existing alert settings), which is the one gap given destructiveHint=true.

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 verb and trigger, and every sentence carries content (allowed values, scoping rules, notification behavior, rate caps). The middle sentences are dense run-ons with the 'after' enumeration awkwardly spliced in, which costs a point but nothing is wasted.

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?

Three optional parameters, no output schema, and the description covers allowed values, default derivation, scoping combinations, notification behavior, and rate-limit impact. The only omission is whether setting an alert replaces a prior configuration and how to remove one entirely.

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%, so the baseline is 3, but the description adds real semantics: 'auto' is derived from job schedule and point spacing with a two-day minimum, and it defines how series and dashboard_id combine to scope the alert. That is meaningfully more than the schema's terse property hints.

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?

States a specific verb (Configure) and resource (stale-data alerts) plus the trigger condition (a series stopped updating). An agent can tell this is about staleness alerting rather than the generic webhook or panel alert siblings, though it never names those siblings 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?

Gives solid in-tool scoping guidance: dashboard_id for every series on a dashboard, series for one series, or both to narrow to one series on one dashboard. However, it never says when to prefer this over set_alert_webhook or set_panel_alert, and no prerequisites or exclusions are stated.

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