InfraNest

Is everything up right now

status_overview

Read-onlyIdempotent

Everything in your organization as it stands right now, in one call: every monitor with its status (up, down, degraded, paused or unknown), when it was last checked and its 24-hour uptime; every server with its state, whether its agent is reporting (null when no agent is installed) and how many of its alert rules are breaching; the open incidents; the maintenance windows running now; and counts of each in summary. Pass tag (a tag ID) to narrow it to monitors and servers with that tag, their incidents, and maintenance that carries the tag or covers them. servers is null when the token has no Cloud scope or your role cannot see servers. Start here for "is anything down": one call covers every monitor, server, open incident and running maintenance.

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": "status_overview"
  }
}

Input Schema

Name	Required	Description	Default
`tag`	No	Only things with this tag id.
`organization_id`	No	The organization to read. Leave it out when the token reaches only one.

Output Schema

Name	Required	Description	Default
`servers`	No
`summary`	No
`monitors`	No
`incidents`	No
`generated_at`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 30, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnly and idempotent, so this earns credit for adding real context: `servers` is null when the token lacks Cloud scope or the role cannot see servers, and the agent-reporting field is null when no agent is installed. These null conditions are exactly the kind of interpretation-critical detail structured fields cannot convey.

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 scope, the returned contents, the tag behavior, and the lead recommendation are front-loaded in a dense but purposeful block. It runs long as a single paragraph, and the closing sentence partially restates the opening scope, which keeps it just under a 5.

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

Completeness5/5

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

With an output schema present, return values need not be explained, yet the description usefully names the key fields and their null cases. For a two-parameter read tool with full annotation coverage, nothing an agent needs to call it correctly is missing.

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 baseline is 3, but the description goes beyond the schema's bare "Only things with this tag id" by explaining that a tag filters monitors, servers, their incidents, and maintenance that either carries the tag or covers the tagged objects. The organization_id omission rule is left to the schema, which already covers it.

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?

The description states a specific verb-less but precise resource scope: every monitor, server, open incident and running maintenance in the organization, with the exact status enum and uptime fields returned. An agent can distinguish this aggregate snapshot from list_monitors, list_servers, or status_across_organizations without opening any schema.

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

Usage Guidelines4/5

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

"Start here for 'is anything down'" gives an explicit entry point and the tag parameter's narrowing behavior is spelled out. However, it never names an alternative such as status_across_organizations for multi-org reads, so the routing guidance stops short of full when-not/alternatives coverage.

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.