Skip to main content
Glama
Sign In

OneUptime

by com.oneuptime
OverviewDiscussionsAdmin

Get Scheduled Maintenance Event

get_scheduled_maintenance_event
Read-only

Get one Scheduled Maintenance Event 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": {
      "id": "<id>"
    },
    "name": "get_scheduled_maintenance_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesID.
selectNoOmit for all but dataStoreIds, openStackParts, subscriberNotificationStatusMessage, customFields, sendSubscriberNotificationsOnBeforeTheEvent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / id / description
      Previous value: -"ID (UUID) of the Scheduled Maintenance Event."New value: +"ID."
    • changedInput schema / properties / select / description
      Previous value: -"Field names to return. Omit for all but these large fields: subscriberNotificationStatusMessage, customFields, sendSubscriberNotificationsOnBeforeTheEvent."New value: +"Omit for all but dataStoreIds, openStackParts, subscriberNotificationStatusMessage, customFields, sendSubscriberNotificationsOnBeforeTheEvent."
  2. Changed2 schema fields changed
    • changedInput schema / properties / id / description
      Previous value: -"The unique identifier (UUID) of the Scheduled Maintenance Event to retrieve. Example: \"550e8400-e29b-41d4-a716-446655440000\""New value: +"ID (UUID) of the Scheduled Maintenance Event."
    • changedInput schema / properties / select / description
      Previous value: -"Optional: field names to return for each Scheduled Maintenance Event (e.g. [\"_id\", \"name\"]). Omit to get all readable fields. Large fields excluded by default (request explicitly if needed): subscriberNotificationStatusMessage, customFields, sendSubscriberNotificationsOnBeforeTheEvent."New value: +"Field names to return. Omit for all but these large fields: subscriberNotificationStatusMessage, customFields, sendSubscriberNotificationsOnBeforeTheEvent."
  3. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that — no note on what is returned, how the 'select' omission behaves, or what happens with an invalid ID.

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?

A single front-loaded sentence with zero filler, which is appropriate in size. It is arguably over-trimmed rather than verbose, but nothing in it is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter read tool with full schema coverage, annotations, and no output schema, the description is barely sufficient. It omits any hint of the returned object or the meaning of the 'select' projection, which is the one genuinely non-obvious aspect of this call.

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%, so both parameters are documented and the baseline of 3 applies. The description only restates that an ID is required and adds no clarification of the unusual 'select' semantics, whose schema text is cryptic about default field selection.

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 ('Get') and resource ('one Scheduled Maintenance Event') plus the lookup key ('by ID'), which is unambiguous. It does not, however, distinguish itself from the many sibling getters or from get_public_status_page_scheduled_maintenance, so an agent must infer the boundary from the name alone.

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

Usage Guidelines2/5

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

No when-to-use guidance is given: nothing says to prefer this over list_scheduled_maintenance_events when the ID is unknown, and no prerequisites or error conditions (e.g., not-found) are mentioned. The single-ID framing implies its usage but states nothing explicitly.

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

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