Skip to main content
Glama

SLA report

get_sla_report
Read-only

Business plans: availability against an SLA target for a range of days in the workspace's time zone (time_zone in get_account; by default this month), with the downtime budget used and left, incidents, MTTR, MTBF and the longest outage, per monitor (lowest availability first) and overall. The dashboard and the API also give it as a PDF. Free.

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
toNoLast day, YYYY-MM-DD.
fromNoFirst day, YYYY-MM-DD, in the workspace's time zone.
targetNoSLA target in percent.
monitor_idsNoOnly these monitors; by default all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description carries real weight here and delivers: plan gating, default this-month range, workspace time zone sourced from get_account, result sort order (lowest availability first), and PDF parity via dashboard/API. The trailing 'Free.' is cryptic and undercuts the otherwise useful access/entitlement disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is one long run-on sentence with a heavy clause chain, and the plan qualifier plus the dangling 'Free.' are front- and back-loaded ambiguously. There is little outright waste, but the structure makes it slower to parse than it needs to be.

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 no output schema, the description compensates well by enumerating the returned metrics and their granularity/sorting, so an agent can decide whether this report satisfies the need. Remaining gaps are entitlement precision (what 'Business plans'/'Free' actually restrict) rather than anything needed to invoke the tool.

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 adds meaning the schema lacks: the default range is 'this month' and the time zone is taken from the workspace/get_account rather than from either date param. It does not clarify monitor_ids scoping beyond the schema's 'by default all'.

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?

The description names a specific resource (SLA availability report against a target) and enumerates its contents: availability, downtime budget used/left, incidents, MTTR, MTBF, longest outage, per monitor and overall. An agent knows exactly what this returns. It stops short of distinguishing itself from near neighbours like get_uptime_history, so it lands at 4 rather than 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 only implied by the product scoping 'Business plans' and the report framing; there is no explicit when-to-use, when-not-to-use, or named alternative. An agent can infer this is the aggregated SLA view rather than raw uptime, but must guess at that boundary.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources