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

iran-cloud-status-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Cloud status now

cs_status
Read-onlyIdempotent

Check live operational status for Iranian cloud providers in one call, showing non-operational components, open incidents, and upcoming maintenance counts to answer 'is X down?'

Instructions

Show the live status of every covered Iranian cloud provider in one call.

Use it first for "is X down?". Per provider: overall status, non-operational components, open incidents, upcoming maintenance count. Next: cs_regions, cs_components, cs_incidents, cs_maintenance.

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_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.7/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, openWorld), so the description's added value is in disclosing the return shape: overall status, non-operational components, open incidents, and maintenance count per provider. It does not mention freshness, caching, or rate limits, which matters somewhat for a 'live' status tool, but the coverage is otherwise solid.

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?

The first sentence establishes purpose and scope, the second states the decision it answers, the third lists the returned fields, and the fourth routes to siblings. Every sentence earns its place and the most important information is front-loaded.

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

Completeness5/5

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

With no parameters and no output schema, the description carries the burden of describing what comes back, and it does so field by field. An agent can decide to call this and interpret the result without consulting anything else.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are zero parameters, so there is nothing for the description to clarify and the baseline of 4 applies. The description correctly implies no input is needed by framing the call as a single global sweep.

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?

The description opens with a specific verb and resource ('Show the live status of every covered Iranian cloud provider') and explicitly scopes it to one call. That scope distinguishes it from the per-resource siblings like cs_providers and cs_components without requiring the agent to open any schema.

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

Usage Guidelines5/5

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

It states an explicit entry point ('Use it first for "is X down?"') and names the follow-up tools (cs_regions, cs_components, cs_incidents, cs_maintenance) so the agent knows what to call next. The routing logic is stated rather than inferred.

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