Skip to main content
Glama

Create application alert

create_application_alert
Destructive

Make an alert on one environment of an Application, on its own measurements: failed requests (failed_share_pct), p95 response time (p95_ms) or restarts. It fires when the reading stays above the threshold for hold_minutes and sends to the places in send_to. The organisation needs a place to send alerts to first (list_alert_destinations), and an application has at most 50 alerts. Needs alerts.manage, or applications.write on the application. In the confirmation, name the application, the environment, the condition and where it sends to.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "application_id": "<application_id>",
      "environment_id": "<environment_id>",
      "name": "<name>",
      "condition": "<condition>",
      "send_to": "<send_to>"
    },
    "name": "create_application_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe alert's name, 1 to 100 characters, for example 'Failed requests'. In the organisation's alert list it reads '<application> · <environment> · <name>'.
send_toYesThe ids of 1 to 5 places the alert sends to, as list_alert_destinations returns them, each named once.
severityNoThe alert's severity. On a create it defaults to warning; on an update leaving it out keeps the alert's severity.
conditionYesWhen the alert fires: the reading of metric stays above threshold for hold_minutes.
application_idYesThe Application's id.
environment_idYesThe id of the environment the alert watches: one of the application's environments (get_application_configuration lists them).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare the safety profile (not read-only, not idempotent, destructive), so the description carries the rest and does: firing semantics (reading stays above threshold for hold_minutes), retention/delivery to send_to, the 50-alert ceiling, required permissions and the mandatory destination prerequisite. The notable gap is that nothing explains the destructiveHint=true for what is nominally a creation call, nor what the 50-alert cap does when exceeded.

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 scope and metrics, then prerequisites and permissions in descending order of importance, with no filler. The opening 'Make an alert on one environment' is slightly informal and the closing confirmation instruction is a behavioural aside rather than definition content, but the paragraph stays compact.

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?

For a 6-parameter nested-object creation tool, the description covers what it makes, when it fires, prerequisites, limits, permissions and even the expected confirmation content. With no output schema, the final sentence about naming application, environment, condition and destination serves as the return-value signal.

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% and every field is already documented with enums, bounds and examples, so the description can only add framing. It does restate the firing relationship between metric, threshold and hold_minutes, but supplies no new syntax or semantics beyond the schema, which matches the baseline of 3.

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 scoped precisely: an alert on one environment of an Application, limited to that application's own measurements. It enumerates the three supported metrics inline (failed_share_pct, p95_ms, restarts), which separates it from the generic alert-creation siblings without requiring the agent to open 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 real preconditions: an alert destination must exist in the organisation first (routing to list_alert_destinations), an application caps at 50 alerts, and the caller needs alerts.manage or applications.write on the application. It does not explicitly contrast with create_alert or update_application_alert, so an agent still has to infer which of those overlapping siblings applies.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.