Skip to main content
Glama

Uptime history

get_uptime_history
Read-only

A monitor's daily uptime, kept for as long as it exists: checks, successful, failed and average response time per UTC day, oldest first. By default from the first check to today. Free.

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": {
      "id": "<id>"
    },
    "name": "get_uptime_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMonitor ID from list_monitors.
toNoLast UTC day, YYYY-MM-DD.
fromNoFirst UTC day, YYYY-MM-DD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description still adds genuine value beyond them: retention ('kept for as long as it exists'), ordering, the default date window, and 'Free' (no quota cost). It omits whether very long histories are paginated or capped, which is the remaining behavioral gap.

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?

Two sentences, no filler, and the content is front-loaded: what is returned first, then the default range. 'Free' is a single word carrying real cost information rather than padding.

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 carries the return-value burden and does so by enumerating the four daily metrics. The only shortfall for a lifetime-history tool is silence on result size or pagination limits, but everything needed to make a correct call is present.

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 schema documents each of the three parameters. The description adds meaning the schema does not — that days are UTC-based, that results are ordered oldest first, and what happens when from/to are omitted — which is exactly the default behavior an agent needs before deciding whether to pass dates.

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 resource (a monitor's daily uptime history) with the exact measures returned — checks, successful, failed, average response time — plus granularity (per UTC day) and sort order (oldest first). It is clearly not a raw-results or incident tool, though it never names a sibling such as get_monitor_results to sharpen the boundary.

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?

The default window ('from the first check to today') gives implied usage context and tells the agent it can call with only an ID. However, there is no explicit statement of when to prefer this over per-check results or SLA reports, and no exclusions or prerequisites beyond the id coming from list_monitors.

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