Skip to main content
Glama

List monitors

list_monitors
Read-only

Every monitor with its current status (pending, up, down, degraded), and interval. Free.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish that this is a safe read operation and closed-world, so the description only needs to add context. It does add meaningful detail: the exact status enum (pending, up, down, degraded), the presence of an interval field, and the cost signal 'Free', which no annotation conveys. Return shape and ordering are still unstated, but that is a modest gap given the annotation coverage.

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?

One fragment, front-loaded with the resource and enumerating the payload contents, with zero filler; the cost note is a single word at the end. The telegraphic style omits a verb and reads more like a docstring than a sentence, which slightly hurts readability without adding waste.

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?

For a zero-parameter read tool with no output schema, the definition covers what an agent most needs to know: it returns all monitors, with status values and interval included, at no cost. Minor gaps are ordering/pagination and whether paused monitors are included, neither of which is likely to block a correct invocation.

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?

The tool takes no parameters, so there is no schema semantics for the description to supplement; the baseline for zero-param tools applies. The description correctly implies there is nothing to filter or scope by.

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?

The description names the resource (every monitor) and the returned fields (current status and interval), and the word 'Every' signals an unfiltered enumeration as opposed to the single-resource sibling get_monitor. It stops short of explicitly naming get_monitor as the alternative for a single monitor, so it is clear but not fully differentiated.

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?

Usage is only implied: 'Every monitor' suggests a full listing, which an agent can read as the bulk-retrieval option versus get_monitor or get_monitor_results. There is no explicit when-to-use, when-not-to-use, or prerequisite statement anywhere in the description.

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