Skip to main content
Glama

slo_budget

Read-onlyIdempotent

Calculates an availability error budget for a chosen period, converting an availability target and period length into allowed downtime and comparing it with used downtime.

Instructions

Calculate an availability error budget for a chosen period.

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": {
      "availabilityPercent": "<availabilityPercent>",
      "periodDays": "<periodDays>"
    },
    "name": "slo_budget"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodDaysYes
availabilityPercentYes
usedDowntimeMinutesNo

Output Schema

NameRequiredDescriptionDefault
kindNo
sourcesNo
exhaustedNo
validatedNo
limitationNo
periodDaysNo
remainingMinutesNo
availabilityPercentNo
usedDowntimeMinutesNo
allowedDowntimeMinutesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.5.0
    • changedInput schema / required
      Previous value: -[
      -  "availabilityPercent",
      -  "periodDays",
      -  "usedDowntimeMinutes"
      -]New value: +[
      +  "availabilityPercent",
      +  "periodDays"
      +]
    • addedOutput schema / properties / sources
      Added value: +{
      +  "type": "array"
      +}
    • addedOutput schema / properties / validated
      Added value: +{
      +  "type": [
      +    "boolean",
      +    "null"
      +  ]
      +}
  2. First observedv0.4.1

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is fully covered. The description adds nothing beyond that: it doesn't say what the calculation does with usedDowntimeMinutes (e.g., whether it reports remaining vs. consumed budget) or how the result is expressed.

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?

One front-loaded sentence with no filler and no repetition of schema or annotation data. It is efficient, though its brevity here reflects under-specification rather than disciplined compression.

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

Completeness2/5

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

It is a small, self-contained calculation and an output schema exists, so return values need not be described. But with 3 undocumented parameters, one of which (usedDowntimeMinutes) has non-obvious default-driven meaning, the description is too thin for an agent to call it confidently without inspecting the schema.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the full burden and does not meet it. 'Availability' loosely maps to availabilityPercent and 'period' to periodDays, but units (percent vs. fraction, days vs. hours) and the entire semantics of the optional usedDowntimeMinutes parameter are left unstated.

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 ('Calculate') and a specific resource ('availability error budget') with a scope ('a chosen period'), so an agent knows exactly what it gets back. It does not, however, distinguish itself from the close sibling latency_budget, which computes a conceptually parallel budget.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this versus latency_budget, or versus capacity_plan / slo-adjacent tools. 'For a chosen period' only hints at an input choice, not at tool selection.

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