Nopaque TotalPath

List Alert Rules

listAlertRules

Read-onlyIdempotent

List the alert rules in your workspace: each says what it watches (a schedule, a saved test or a batch, named by targetLabel), what it alerts on (failed runs, M of the last N), whether it is enabled or muted, its state now (OK or IN_ALARM) and since when, and the email destinations it sends to with their verification status. misconfigured is true for an enabled rule with no verified destination, which means nobody is told. Takes no parameters. Use when: the user asks what alerts are set up, whether something is alerting, or why nobody was emailed. Read-only. Needs notifications:read. Only a person signed in to the nopaque web app can call this (the in-app assistant); an API key is refused.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`count`	Yes
`rules`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive, closed-world), the description adds the auth model ('only a person signed in to the nopaque web app… an API key is refused'), the required scope (notifications:read), and the meaning of the derived `misconfigured` flag. These are behavioral facts an agent cannot recover from structured fields.

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 field enumeration is a long single sentence but every element listed is substantive, and the usage, auth, and permission constraints follow in short clauses. Slightly denser than ideal, but nothing is padding.

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, the description need not explain return shapes, yet it still summarizes the salient fields and the one derived flag that matters operationally. Auth constraints, scope, and no-parameter behavior are all covered, leaving nothing an agent needs 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?

There are zero parameters, so the baseline is 4; the description explicitly states 'Takes no parameters', confirming no filtering is possible and that the caller must scope results client-side. That is a small but real addition beyond the empty 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?

The description opens with a specific verb and resource ('List the alert rules in your workspace') and then enumerates exactly what each rule contains — targetLabel, alert condition, enabled/muted, OK/IN_ALARM state and since, email destinations with verification status. That level of detail distinguishes it clearly from the singular getAlertRule sibling.

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?

It provides an explicit 'Use when:' clause with three concrete user intents (what alerts are set up, whether something is alerting, why nobody was emailed). It does not name getAlertRule as the alternative for fetching a single rule, so the routing guidance is strong but not exhaustive.

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

All Nopaque TotalPath 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.