Skip to main content
Glama
tp322d

LastPing

by tp322d
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

create_destination

Create a notification destination so monitors can route alerts to it. Choose a kind (webhook, chat, email, etc.) and receive a channel ID to use in routes.

Instructions

Requires an API key with the write scope or higher. Create a notification destination (channel) that monitors can route alerts to. Provide the fields for the chosen kind; unrelated fields are ignored. Non-email kinds are usable immediately; email kinds are created unverified and send a confirmation link that must be clicked before they can be attached to a route. A project holds at most 25 destinations — if creation is refused with DESTINATION_CAP_REACHED, delete one with delete_destination rather than retrying. Returns the new channel id — pass it to set_route.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNowebhook: the POST target URL.
kindYesOne of: webhook, telegram, discord, slack, ntfy, pushover, msteams, googlechat, email. Every destination URL must be https. A BRANDED kind must point at its vendor's host: discord at discord.com or discordapp.com, slack at hooks.slack.com, msteams at webhook.office.com or outlook.office.com or logic.azure.com or logic.azure.us or environment.api.powerplatform.com, googlechat at chat.googleapis.com. For any other endpoint use kind "webhook", which accepts any https host; ntfy is unpinned too, so a self-hosted ntfy server is fine. A pin narrows the destination to the vendor's own platform; it does NOT prove the endpoint belongs to the person or project that created it, because every pinned domain is multi-tenant and open to anyone who signs up. Do not report a pinned destination as verified or as owned by anyone on the strength of its host.
nameYesHuman-readable destination name, e.g. 'On-call Slack'.
tokenNopushover: the application API token.
secretNowebhook: shared secret used to sign the HMAC-SHA256 payload.
addressNoemail: the destination email address (a confirmation link is sent).
chat_idNotelegram: the target chat id.
user_keyNopushover: the user or group key.
bot_tokenNotelegram: the bot token from @BotFather.
topic_urlNontfy: the full topic URL, e.g. 'https://ntfy.sh/my-topic'.
webhook_urlNoslack / discord / msteams / googlechat: the incoming-webhook URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.6
    • changedInput schema / properties / kind / description
      Previous value: -"One of: webhook, telegram, discord, slack, ntfy, pushover, msteams, googlechat, email. Every destination URL must be https. A BRANDED kind must point at its vendor's host: discord at discord.com or discordapp.com, slack at hooks.slack.com, msteams at webhook.office.com or outlook.office.com or logic.azure.com or logic.azure.us or environment.api.powerplatform.com, googlechat at chat.googleapis.com. For any other endpoint use kind \"webhook\", which accepts any https host; ntfy is unpinned too, so a self-hosted ntfy server is fine. A pin narrows the destination to the vendor's own platform; it does NOT prove the endpoint belongs to the person or project that created it, because every pinned domain is multi-tenant and self-service. Do not report a pinned destination as verified or as owned by anyone on the strength of its host."New value: +"One of: webhook, telegram, discord, slack, ntfy, pushover, msteams, googlechat, email. Every destination URL must be https. A BRANDED kind must point at its vendor's host: discord at discord.com or discordapp.com, slack at hooks.slack.com, msteams at webhook.office.com or outlook.office.com or logic.azure.com or logic.azure.us or environment.api.powerplatform.com, googlechat at chat.googleapis.com. For any other endpoint use kind \"webhook\", which accepts any https host; ntfy is unpinned too, so a self-hosted ntfy server is fine. A pin narrows the destination to the vendor's own platform; it does NOT prove the endpoint belongs to the person or project that created it, because every pinned domain is multi-tenant and open to anyone who signs up. Do not report a pinned destination as verified or as owned by anyone on the strength of its host."
  2. Changed1 schema field changedv0.1.3
    • changedInput schema / properties / kind / description
      Previous value: -"One of: webhook, email, slack, discord, telegram, ntfy, pushover, msteams, googlechat."New value: +"One of: webhook, telegram, discord, slack, ntfy, pushover, msteams, googlechat, email. Every destination URL must be https. A BRANDED kind must point at its vendor's host: discord at discord.com or discordapp.com, slack at hooks.slack.com, msteams at webhook.office.com or outlook.office.com or logic.azure.com or logic.azure.us or environment.api.powerplatform.com, googlechat at chat.googleapis.com. For any other endpoint use kind \"webhook\", which accepts any https host; ntfy is unpinned too, so a self-hosted ntfy server is fine. A pin narrows the destination to the vendor's own platform; it does NOT prove the endpoint belongs to the person or project that created it, because every pinned domain is multi-tenant and self-service. Do not report a pinned destination as verified or as owned by anyone on the strength of its host."
  3. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only indicate non-readonly, non-open-world, non-idempotent, non-destructive. The description adds substantial behavioral detail: email kinds are created unverified, a confirmation link is required, unrelated fields are ignored, and host pinning does not prove ownership. It also explains the cap behavior on failure.

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?

Dense but well-organized, with the most important constraints front-loaded. Every sentence delivers specific operational knowledge, from authentication through creation, verification, cap handling, and post-creation use.

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?

Given the large parameter set and no output schema, the description covers prerequisites, side effects, failure modes, return value, and downstream usage. This is more than sufficient for an agent to select and correctly invoke the tool.

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 description does not need to restate parameter docs. It adds value beyond the schema by explaining that unrelated fields are ignored and that fields should be selected according to the chosen kind, which clarifies a likely point of confusion for callers.

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?

The description states a specific action ('Create a notification destination'), names the resource ('channel'), and clarifies its purpose ('monitors can route alerts to'). It clearly distinguishes from related siblings like set_route, update_destination, and delete_destination.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Provides explicit context: required API scope, which kinds are usable immediately versus email needing verification, the 25-destination cap, and the specific DESTINATION_CAP_REACHED fallback of deleting a destination. It also directs the caller to pass the new id to set_route, giving clear next steps.

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