InfraNest

Uptime and response times of a monitor

monitor_stats

Read-onlyIdempotent

Uptime for the last 24 hours, 7 days and 30 days, incident counts, response-time figures and chart series for the chosen period (24h, 7d or 30d, default 24h). Pass region to narrow the figures to one probe region; the regions with data are listed in regions. Uptime, response times and incidents over 24h, 7d or 30d, drawn as a chart where the client supports it. For a calendar month for a customer use uptime_report; for single checks monitor_results.

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": {
      "monitor_id": "<monitor_id>"
    },
    "name": "monitor_stats"
  }
}

Input Schema

Name	Required	Description
`period`	No	How far back (default 24h).
`region`	No	Only checks from this probe region.
`monitor_id`	Yes	The monitor id, from list_monitors or the number of a search hit monitor:N.
`organization_id`	No	The organization to read. Leave it out when the token reaches only one.

Output Schema

Name	Required	Description	Default
`period`	No
`uptime`	No
`app_url`	No
`chart_data`	No
`response_time`	No
`incident_stats`	No
`uptime_chart_data`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026

changedInput schema / properties / monitor_id / description

Previous value: -"The monitor id, from list_monitors."New value: +"The monitor id, from list_monitors or the number of a search hit monitor:N."

First observedOct 30, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered; the description adds the useful non-obvious behavior that region figures depend on available probe data and are echoed in `regions`, plus the default period. It does not discuss rate limits or pagination, but for a read-only stats fetch that is minor.

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?

The scoping and alternatives are front-loaded, but the third sentence ('Uptime, response times and incidents over 24h, 7d or 30d, drawn as a chart where the client supports it') largely restates the first without new information. Removing it would lose nothing.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile; the description still conveys what categories of data come back and how to scope by region and period. Only the organization-scoping caveat is left entirely to the schema, which is acceptable at 100% coverage.

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 baseline is 3; the description still adds value by spelling out the period enum and default in prose and by clarifying that `region` narrows figures to a single probe region whose valid values come from the `regions` field of the response. It says nothing about `monitor_id` or `organization_id`, but both are already documented in-schema.

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?

Opens with a concrete verb+resource and enumerates exactly what is returned: uptime over three windows, incident counts, response-time figures and chart series. It also distinguishes itself from the two most confusable siblings by name (uptime_report, monitor_results), so an agent can route without opening a schema.

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

Usage Guidelines5/5

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

Explicitly states when to use an alternative: 'For a calendar month for a customer use uptime_report; for single checks monitor_results.' It also explains how to obtain a valid `region` (regions with data are listed in `regions`), removing the main usage ambiguity.

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

All InfraNest 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.