Skip to main content
Glama
Sign In

Exit1 Uptime Monitoring

by dev.exit1
OverviewDiscussionsAdmin

Get SLA report

get_sla_report
Read-onlyIdempotent

SLA reports (Pro plan). Without report_id, list the account's SLA reports with this month's availability, target and status. With report_id, get one month: availability vs target, error budget, per-check numbers and the 20 longest incidents, with times in the report's time zone. Availability counts confirmed downtime only; maintenance, firewall-blocked probes and unmonitored time are excluded.

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": "get_sla_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodNoMonth as YYYY-MM in the report's time zone (default: the current month)
report_idNoThe SLA report ID from a list call. Omit to list reports.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the read-only, idempotent, non-destructive annotations, the description discloses substantive semantics: plan gating, the availability computation rule (confirmed downtime only; maintenance, firewall-blocked probes and unmonitored time excluded), the time-zone basis of returned timestamps, and the exact contents of the detail payload. That is precisely the kind of context annotations cannot carry.

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?

Three sentences, no filler: mode routing first, detail payload second, calculation caveat third. The order is front-loaded with the decision the caller must make before anything else.

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 output schema, the description carries the return-value burden itself and does so by enumerating the detail payload fields and the list-call summary fields. Both optional parameters are accounted for and the entitlement constraint is stated, so an agent has everything needed to call this correctly.

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?

Schema coverage is 100%, so the baseline is 3, but the description goes further by explaining that report_id is a mode switch rather than a filter, that the detail covers one month, and that times are rendered in the report's time zone. The period parameter's interaction with the detail call is only implied ("one month"), leaving a minor gap.

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?

Names a specific resource (SLA reports) and splits behavior into two explicit modes: list when report_id is omitted, single-month detail when it is supplied. The scope of the returned data (availability vs target, error budget, per-check numbers, 20 longest incidents) makes the tool unmistakable against any sibling such as get_check_stats or get_check_history.

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?

The two-mode routing rule ("Without report_id, list...", "With report_id, get one month") tells an agent exactly which call shape to use for discovery vs detail, and "(Pro plan)" flags an entitlement prerequisite. It does not, however, name an alternative tool or state what to do if the plan is insufficient, so it stops short of full when/when-not guidance.

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

All Exit1 Uptime Monitoring toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources