Skip to main content
Glama

LastPing

by dev.lastping
OverviewDiscussionsAdmin

Update alert destination

update_destination
DestructiveIdempotent

Requires the write scope or higher. Updates a notification destination's name and/or config in place; only the supplied fields change. The kind cannot change (delete and recreate instead). A new email address resets verification and sends a new confirmation email.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoNew human-readable label. Omitted: unchanged.
configNoReplacement config for the destination's existing kind (webhook, telegram, discord, slack, ntfy, pushover, msteams, googlechat, email), naming only that kind's fields, each once: {url,secret} webhook, {bot_token,chat_id} telegram, {webhook_url} slack/discord/msteams/googlechat, {topic_url,token} ntfy, {token,user_key} pushover, {address} email. Omitted: unchanged. A secret left out is kept only while the webhook url / ntfy topic_url is unchanged (else 400: resend it); "" clears the ntfy token; other fields left out are removed. A supplied URL has to be https on the kind's allowed hosts (older destinations keep working until replaced). The host rule does not prove who owns the endpoint.
destination_idYesUUID of the destination to update, from list_destinations.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / config / description
      Previous value: -"Replacement config for the destination's existing kind — one of webhook, telegram, discord, slack, ntfy, pushover, msteams, googlechat, email. Shape must match the kind: {\"url\":…,\"secret\":…} for webhook, {\"bot_token\":…,\"chat_id\":…} for telegram, {\"webhook_url\":…} for slack/discord/msteams/googlechat, {\"topic_url\":…} for ntfy, {\"token\":…,\"user_key\":…} for pushover, {\"address\":…} for email. Omit to leave unchanged. A URL you supply is re-checked against the kind's allowed hosts and must be https; a destination created before that rule keeps working until you send a new config for it. The config must name only the fields listed for its kind, each exactly once. The host rule narrows a branded destination to the vendor's own platform; it does NOT prove the endpoint belongs to the person or project that owns the destination."New value: +"Replacement config for the destination's existing kind (webhook, telegram, discord, slack, ntfy, pushover, msteams, googlechat, email), naming only that kind's fields, each once: {url,secret} webhook, {bot_token,chat_id} telegram, {webhook_url} slack/discord/msteams/googlechat, {topic_url,token} ntfy, {token,user_key} pushover, {address} email. Omitted: unchanged. A secret left out is kept only while the webhook url / ntfy topic_url is unchanged (else 400: resend it); \"\" clears the ntfy token; other fields left out are removed. A supplied URL has to be https on the kind's allowed hosts (older destinations keep working until replaced). The host rule does not prove who owns the endpoint."
    • changedInput schema / properties / destination_id / description
      Previous value: -"UUID of the destination to update. Get it from list_destinations."New value: +"UUID of the destination to update, from list_destinations."
    • changedInput schema / properties / name / description
      Previous value: -"New human-readable label. Omit to leave unchanged."New value: +"New human-readable label. Omitted: unchanged."
  2. Changed1 schema field changed
    • changedInput schema / properties / config / description
      Previous value: -"Replacement config for the destination's existing kind — one of webhook, telegram, discord, slack, ntfy, pushover, msteams, googlechat, email. Shape must match the kind: {\"url\":…,\"secret\":…} for webhook, {\"bot_token\":…,\"chat_id\":…} for telegram, {\"webhook_url\":…} for slack/discord/msteams/googlechat, {\"topic_url\":…} for ntfy, {\"token\":…,\"user_key\":…} for pushover, {\"address\":…} for email. Omit to leave unchanged."New value: +"Replacement config for the destination's existing kind — one of webhook, telegram, discord, slack, ntfy, pushover, msteams, googlechat, email. Shape must match the kind: {\"url\":…,\"secret\":…} for webhook, {\"bot_token\":…,\"chat_id\":…} for telegram, {\"webhook_url\":…} for slack/discord/msteams/googlechat, {\"topic_url\":…} for ntfy, {\"token\":…,\"user_key\":…} for pushover, {\"address\":…} for email. Omit to leave unchanged. A URL you supply is re-checked against the kind's allowed hosts and must be https; a destination created before that rule keeps working until you send a new config for it. The config must name only the fields listed for its kind, each exactly once. The host rule narrows a branded destination to the vendor's own platform; it does NOT prove the endpoint belongs to the person or project that owns the destination."
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well past the annotations: partial-update semantics ("only the supplied fields change"), the immutability of `kind`, and a side effect the annotations never capture ("A new email address resets verification and sends a new confirmation email"). destructiveHint=true is consistent with the note that omitted config fields are removed and a resend is required.

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?

Three tightly packed sentences with zero filler: permission requirement first, mutation semantics second, the non-obvious email side effect last. Every sentence earns its place.

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?

For a write tool with a nested config object and no output schema, the description covers permissions, partial-update behavior, immutability, and the email verification side effect. The only gap is that it says nothing about what the call returns or how the reset verification surfaces to the caller.

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%, with the config retention, secret, and host rules fully documented in the schema itself, so the baseline is 3. The description reinforces "only the supplied fields change" but adds almost no parameter meaning the schema does not already carry.

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+resource ("Updates a notification destination's name and/or config in place") and immediately differentiates from siblings by ruling out kind changes and pointing to delete+recreate. An agent can distinguish it from create_destination, delete_destination, and test_destination without opening any schema.

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?

Prerequisites are explicit ("Requires the write scope or higher") and it routes the kind-change case to the alternative workflow ("delete and recreate instead"). It does not, however, contrast the tool with test_destination or explain when a re-verification round-trip is acceptable, so usage guidance is clear but not exhaustive.

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

All LastPing 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