Skip to main content
Glama
tp322d

LastPing

by tp322d
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

update_destination

DestructiveIdempotent

Update a notification destination's name or config without changing its kind. Specify only the fields to modify; email changes require re-verification.

Instructions

Requires an API key with the write scope or higher. Update a notification destination's name and/or config in place. Only the fields you pass are changed. The destination kind cannot be changed — delete and recreate instead. Changing an email destination's address resets verification and sends a new confirmation email.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoNew human-readable label. Omit to leave unchanged.
configNoReplacement 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.
destination_idYesUUID of the destination to update. Get it from list_destinations.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Excellent disclosure beyond annotations: auth scope requirement, partial-update semantics ('Only the fields you pass are changed'), immutability of kind, and the side effect that changing email address resets verification and sends a confirmation email. These are critical behaviors not captured by annotations alone.

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, each earning its place. Auth requirement front-loaded, then the core action, then the immutability constraint, then the notable side effect. Zero waste.

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?

Complete for a mutation tool. Annotations cover safety (destructive), description covers auth, partial-update behavior, immutability, and side effects. No output schema exists but none is needed for this update operation. Nothing critical is missing.

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 schema thoroughly documents each parameter including the complex nested config shape. The description reinforces partial-update semantics but doesn't add much beyond the schema. Baseline 3, raised to 4 for reinforcing the 'omit to leave unchanged' contract and the config kind constraint.

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 ('Update a notification destination's name and/or config in place') and clearly distinguishes from sibling delete_destination and create_destination. The scope of what can be updated (name/config only) is explicit.

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?

Provides when-to-use context by stating the kind cannot be changed and pointing to delete-and-recreate as the alternative. Also states auth requirement. However, it doesn't explicitly name the sibling tools or contrast with test_destination/create_destination.

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