Skip to main content
Glama

instatus

by io.usefulapi

Update maintenance

instatus_update_maintenance
Destructive

UPDATES an existing scheduled maintenance by id — this MODIFIES live status-page data and can notify subscribers. Send only the fields you want to change. Instatus: PUT /v1/{page_id}/maintenances/{maintenance_id}. Returns the updated maintenance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNoISO 8601 timestamp for when the maintenance ends.
nameNoMaintenance title.
startNoISO 8601 timestamp for when the maintenance starts.
notifyNoWhether to notify subscribers about this update.
statusNoMaintenance status.
messageNoMaintenance update message (Markdown supported).
page_idYesThe status page's id.
durationNoMaintenance duration in minutes.
statusesNoPer-component impact — set each listed component's status for this event.
componentsNoComponent ids affected by this maintenance.
maintenance_idYesThe maintenance's id to update.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations provide destructiveHint=true. Description adds that it modifies live data and can notify subscribers, adding value beyond annotations. No contradictions.

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?

Two sentences plus an endpoint note; no wasted words. Every sentence adds essential information.

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?

Covers purpose, effect, usage pattern, and endpoint. No output schema is needed given the natural expectation of returning updated maintenance. Good balance for a mutation tool.

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% with detailed descriptions. The description adds general guidance ('send only fields to change') but no per-parameter insights beyond schema.

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?

Clear verb 'UPDATES' and resource 'existing scheduled maintenance' with specific context. Distinguishes from siblings (create, delete, get, list) by focusing on modification.

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?

States 'this MODIFIES live status-page data and can notify subscribers' and 'Send only the fields you want to change', providing clear usage context. Lacks explicit contrast with alternative tools but sufficient for understanding.

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

All instatus toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool targets a distinct resource (component, incident, maintenance, page) and action (create, get, list, update, delete). There is no overlap or ambiguity between tool purposes.

Naming Consistency5/5

All tools follow the pattern 'instatus_<action>_<resource>' in snake_case. Names are predictable and consistent across all 14 tools.

Tool Count5/5

14 tools cover the core operations for status page management (components, incidents, maintenances, pages) without being excessive. The number feels appropriate for the domain.

Completeness4/5

Incidents and maintenances have full CRUD coverage. Components lack create and delete tools, and pages have only list. These are minor gaps that may require out-of-band management.

Resources