Skip to main content
Glama
lastping-dev

LastPing

by lastping-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

Update alert destination

update_destination
DestructiveIdempotent

Update a LastPing notification destination's name or config in place, changing only supplied fields. A new email address resets verification.

Instructions

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":…} 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. Omitted: unchanged. A supplied URL is re-checked against the kind's allowed hosts and has to be https; a destination created before that rule keeps working until its config is 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 changedv0.1.17
    • 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\":…} 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. Omitted: unchanged. A supplied URL is re-checked against the kind's allowed hosts and has to be https; a destination created before that rule keeps working until its config is 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 changedv0.1.3
    • 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.6/5.0
Behavior5/5

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

Annotations already declare idempotent/destructive/not-read-only, and the description adds substantial context on top: the required write scope, that only supplied fields are mutated (partial update, a real behavioral trait), that 'kind' is immutable, and that supplying a new email resets verification and triggers a confirmation email.

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?

Four tight sentences, front-loaded with the scope requirement, then update semantics, then the immutability constraint, then the side effect. No filler; each sentence contributes a distinct operational fact.

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 mutation tool with no output schema, the description covers auth, mutation semantics, constraints, and side effects well. It stops short of describing the response shape or what the updated destination returns, which is the only notable gap.

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 per-parameter documentation is already carried by the schema (baseline 3). The description adds cross-parameter semantics the schema does not: partial-update behavior ('only the supplied fields change') and the kind-immutability constraint tying config changes to the existing kind.

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 and resource ('updates a notification destination's name and/or config in place') with field-level scope, and explicitly carves out what it is not: the kind cannot change. An agent can distinguish it from delete_destination/create_destination 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear prerequisite ('Requires the write scope or higher') and names the alternative path when the change isn't supported ('delete and recreate instead'). It doesn't broadly contrast with create_destination for new destinations, but the routing guidance is concrete.

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