Skip to main content
Glama
Sign In
iran-cloud-status-mcp

iran-cloud-status-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Planned maintenance

cs_maintenance
Read-onlyIdempotent

Lists upcoming, running, or recently finished maintenance windows per Iranian cloud provider, returning an empty result when none are announced.

Instructions

List announced maintenance windows that are upcoming or running, per provider, optionally with recent finished ones.

Empty means nothing is announced.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cs_maintenance"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoWith include_past: look-back days.
providerNoOne provider; leave out for all that support this tool.
include_pastNoAlso list finished windows from the last `days` days.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuinely useful behavior beyond them: the default result set is upcoming plus running windows, and an empty result explicitly means 'nothing announced' rather than an error. It does not describe pagination or result volume, so it is not a 5.

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 short sentences with zero filler; the core scope comes first and the empty-result caveat is a compact, high-value closer.

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?

For a three-optional-parameter list tool the description covers default behavior, the include_past option, and empty-result semantics. Since there is no output schema, it would help to say what a maintenance window entry contains (provider, window start/end, state), which is the only remaining gap.

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 all three parameters are already documented in the schema. The description only paraphrases them ('per provider', 'optionally with recent finished ones') and adds no format or interaction detail beyond what the schema states. 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 ('List announced maintenance windows') plus the scope ('upcoming or running, per provider'). This separates it from cs_incidents and cs_status by resource, though it never names a sibling explicitly, so it falls short of a 5.

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?

Usage is implied rather than stated: an agent can infer this is the tool for planned downtime, but there is no explicit when-to-use or when-not-to-use guidance against cs_incidents or cs_status. The default scope (upcoming/running) is described, which helps select the tool without further parameters.

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