Fixter

Get Uptime

get_uptime

Read-onlyIdempotent

Compute an API test's uptime percentage over a window, plus latency percentiles and run counts. Uptime = SUCCESS / (SUCCESS + FAILURE); ERROR, MISSED and RATE_LIMITED runs are excluded. Defaults to the last 24 hours when no window is given. 'latencyAvg' is the plain average, and 'avgSteps', 'p50Steps', 'p95Steps' and 'p99Steps' average each step's phases over all runs, the slower half, the slowest 5% and the slowest 1% of runs, so a slow percentile can be read as DNS, handshake, server or download time. The steps are the same list, in the same order, as on the test's runs.

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": {
      "apiTestId": "<apiTestId>"
    },
    "name": "get_uptime"
  }
}

Input Schema

Name	Required	Description
`to`	No	End of the window, ISO-8601 instant; defaults to now
`from`	No	Start of the window, ISO-8601 instant; defaults to 24h before 'to'
`apiTestId`	Yes	Id of the API test to report on

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 16, 2026
- addedInput schema / $schema
```
Added value: +"https://json-schema.org/draft/2020-12/schema"
```
- removedInput schema / additionalProperties
```
Removed value: -false
```
AddedSep 19, 2026
RemovedSep 19, 2026
AddedAug 12, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations already cover the read-only/idempotent safety profile, and the description goes well beyond them: it defines the uptime formula, names exactly which run statuses are excluded (ERROR, MISSED, RATE_LIMITED), and explains what each latency/step percentile aggregates. That is real computational semantics an agent cannot get from annotations.

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?

The core purpose and the window default are front-loaded in the first two sentences. The latter half is dense with output-field definitions (avgSteps, p50/p95/p99Steps) but each clause clarifies a distinct returned value, so it mostly earns its place despite the length.

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 correctly spends its space explaining return semantics — formulas, exclusions, and percentile meaning. Remaining gaps are minor edge cases: behavior with an empty run set in the window, and whether the reported run counts include the excluded statuses.

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

Parameters3/5

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

Schema coverage is 100%, so 'from', 'to', and 'apiTestId' are already documented in the schema, including the same 24h/'now' defaults. The description reinforces the window semantics but adds no new constraint, format, or validation detail. Baseline 3 applies when the schema carries the parameter burden.

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?

States a specific verb and resource — compute an API test's uptime percentage — and enumerates the accompanying outputs (latency percentiles, run counts). This clearly separates it from siblings like get_api_test_runs (raw runs) or get_api_test (config), so an agent can select it without opening the schema.

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 description supplies a default window ('last 24 hours when no window is given'), which implies when the tool is applicable. However, it never states when to prefer this over get_api_test_runs or get_api_test, nor any when-not condition. Usage is implied rather than directed.

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

All Fixter tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?