Skip to main content
Glama
Sign In

Phare

by io.phare.mcp
OverviewDiscussionsAdmin

Delete a maintenance window

delete_maintenance_window
DestructiveIdempotent

Delete a maintenance window by ID in any state, it disappears from the status pages and the monitors it paused are resumed. This cannot be undone and triggers no alert rule.

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": {
      "project_id": "<project_id>",
      "maintenance_window_id": "<maintenance_window_id>"
    },
    "name": "delete_maintenance_window"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesID of the project to act on, see whoami
maintenance_window_idYesID of the maintenance window to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing concrete consequences: the window disappears from status pages, monitors it paused are resumed, the action is irreversible, and no alert rule is triggered. For a destructiveHint=true mutation this is exactly the side-effect and notification information an agent needs before calling it.

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?

A single well-packed sentence: the action leads, the side effects and irreversibility follow. No filler, and every clause carries information an agent needs.

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?

Complete on effects, irreversibility, and notification silence for a two-parameter delete with no output schema. The remaining gap is the missing guidance on when to delete versus cancel or complete a window, which matters given three overlapping siblings.

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 coverage is 100%, so both parameters are already documented, including the pointer to whoami for project_id. The description adds only 'by ID' and does not clarify project scoping or ID semantics beyond the schema, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Delete a maintenance window by ID') and adds scope ('in any state'). It does not name or differentiate itself from close siblings like cancel_maintenance_window or complete_maintenance_window, so an agent must infer the distinction from the names alone.

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

Usage Guidelines3/5

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

'in any state' implies the tool works regardless of window status, which partially distinguishes it from cancel/complete siblings, but there is no explicit when-to-use statement or exclusion naming the alternatives. Usage is inferable rather than stated.

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

All Phare toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources