Skip to main content
Glama
Sign In

InfraNest

by io.infranest
OverviewDiscussionsAdmin

End a maintenance window now

end_maintenance
Idempotent

Marks a running maintenance window as done, so its monitors and servers alert again. Ended before its planned end, the window ends now: reports and uptime count only the time it ran.

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": {
      "maintenance_id": "<maintenance_id>"
    },
    "name": "end_maintenance"
  }
}

Input Schema

NameRequiredDescriptionDefault
maintenance_idYesThe maintenance window id, from list_maintenance_windows or status_overview.
organization_idNoThe organization. Leave it out when the token reaches only one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Goes beyond the annotations by explaining the observable effect ('monitors and servers alert again') and the early-termination semantics (reports and uptime count only the time it ran), which the agent could not derive from readOnlyHint/idempotentHint alone. Missing only auth/error behavior.

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?

Two short sentences, effect stated first and the nuance about early ending second. Slightly awkward phrasing ('Ended before its planned end, the window ends now') is the only cost.

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?

With annotations covering safety and idempotency, a fully described schema, and no output schema, the description supplies what remains: the post-condition and the accounting behavior on early termination. Sufficient to invoke correctly.

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 maintenance_id and organization_id are already fully documented in the schema. The description adds no additional parameter guidance, so baseline 3 applies.

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?

Specific verb and resource: 'marks a running maintenance window as done', with the immediate consequence stated. This clearly separates it from start_maintenance and list_maintenance_windows in the sibling set.

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?

The word 'running' implies the precondition that a window must be active, but there is no explicit statement of when to use this versus start_maintenance or how to find the window first. 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 InfraNest 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