Skip to main content
Glama
Sign In

BorealHost

by ai.borealhost
OverviewDiscussionsAdmin

delete_alert_rule

Delete an alert rule.

Requires: API key with write scope.

Args: slug: Site identifier rule_id: UUID of the alert rule to delete

Returns: {"deleted": true, "id": "uuid"}

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": {
      "slug": "<slug>",
      "rule_id": "<rule_id>"
    },
    "name": "delete_alert_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes
rule_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

No annotations are present, so the description carries the burden. It discloses the permission requirement (write scope) and states the return value format, which is useful behavioral context. Does not mention error cases or idempotency, but the core behavior is clear.

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?

Compact and well-structured: purpose in one line, then Requires/Args/Returns. No fluff, every sentence adds value.

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 simple delete operation with no annotations or output schema, the description covers purpose, auth requirement, parameter meanings, and return format. Sufficient for an agent to select and invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 0% description coverage, but the description fully documents both parameters: 'slug: Site identifier' and 'rule_id: UUID of the alert rule to delete'. This compensates completely and adds type constraints (UUID).

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?

Description states 'Delete an alert rule' — a specific verb and resource. It clearly distinguishes from sibling tools like create_alert_rule and list_alert_rules.

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 clear context: requires API key with write scope. Doesn't explicitly mention alternatives, but the action itself implies when to use it (when deleting, not creating or listing).

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

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