Skip to main content
Glama
Sign In
vibeMK

vibeMK

by chexma
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

vibemk_delete_downtime

Cancel a scheduled or active downtime by its ID to restore monitoring immediately.

Instructions

🗑️ Delete downtime - Cancel a scheduled or active downtime by ID

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": {
      "downtime_id": "<downtime_id>"
    },
    "name": "vibemk_delete_downtime"
  }
}

Input Schema

NameRequiredDescriptionDefault
downtime_idYesDowntime ID to delete (get from list_downtimes)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.10

TDQS

A4/5.0
Behavior3/5

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

Does not disclose any side effects such as whether the deletion is reversible, requires activation, or has restrictions; with no annotations, the description bears the burden and it is somewhat lacking.

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?

One clear sentence with an icon, no unnecessary words.

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?

Sufficient for a simple delete operation; does not mention return values or failure modes, but no output schema exists.

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?

The parameter downtime_id is already described in the schema as the ID to delete and where to get it; the tool description adds no further semantics.

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?

Clearly states it deletes/cancels a downtime by ID, distinguishing from schedule and list tools.

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?

Implicitly indicates usage: you need an existing downtime ID, likely from list/downtime tools; does not explicitly contrast with alternatives but is understandable.

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