Skip to main content
Glama

Error budgets

get_error_budgets
Read-only

Every monitor with an availability objective (slo_target over slo_window_days, set with update_monitor): its availability over the rolling window, the error budget in seconds, how much is used and left, the last hour's burn rate and whether it burns fast, least budget left first. Every plan. 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_error_budgets"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this a read-only, closed-world operation, and the description adds genuinely useful behavior on top: result ordering (least budget left first), the inclusion filter (only monitors with an objective), and the fact that the last hour's burn rate is summarized with a fast-burn verdict. "Every plan. Free." also pre-empts a subscription-gating question an agent might otherwise raise.

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?

Single sentence, front-loaded with the scope and then the returned fields in a colon-delimited list, with the sort order placed as a natural closing clause. It is dense but every clause carries information; the choppy "Every plan. Free." fragments are the only stylistic cost.

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 parameters and no output schema, the description bears the full burden of describing the return payload, and it does so field by field. Only the top-level response shape (array of monitor records vs. an object keyed by monitor) is left unspecified, which is a minor gap for an agent parsing the result.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The mention of slo_target and slo_window_days correctly attributes those fields to update_monitor rather than implying they are inputs here.

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?

Names the resource precisely and scopes it ("Every monitor with an availability objective\"), then enumerates exactly what each row contains: availability, budget in seconds, used/left, burn rate, fast-burn flag. That is far beyond a tautology. It does not name a sibling to contrast with (e.g. get_sla_report), so it stops 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: "least budget left first" signals the tool is for finding monitors about to exhaust budget, and the parenthetical about slo_target/slo_window_days set with update_monitor explains the prerequisite configuration. There is no explicit when-to-use versus when-not guidance or named alternative.

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