Skip to main content
Glama

List monitors

list_monitors

Lists website monitors in a monity.ai account with names, URLs, status, labels, and check times so you can find a monitor UUID and filter results by workspace, label, or active state.

Instructions

List the website monitors (tasks) in the monity.ai account: name, monitored URL, type, active state, labels, and last/next check times. Use this first to find a monitor's uuid for the other tools.

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
pageNoPage number (default 1)
labelNoFilter by label name
limitNoResults per page (default 25, max 100)
activeNoFilter by active state
workspaceIdNoOnly monitors in this workspace (from list_workspaces)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden, and it does convey that this is a read-only enumeration and what data comes back. It says nothing about permissions, default ordering, or how pagination behaves in practice, even though the paged nature of the result materially affects how an agent should consume it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no filler, with the identity of the resource front-loaded and the field inventory following. The field list earns its place because there is no output schema to convey the return shape.

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 five-parameter, zero-required list tool with no output schema and no annotations, the description covers purpose, return fields, and its role in a workflow. The only real gap is that paging and filtering behavior must be inferred entirely from the schema.

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 description coverage is 100%, with page, limit, label, active, and workspaceId all documented in the schema, so the baseline is 3. The description adds no parameter-level meaning beyond that — no mention that results can be filtered or paged at all.

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 gives a specific verb and resource ("List the website monitors (tasks)") scoped to the monity.ai account, and enumerates the fields returned (name, URL, type, active state, labels, check times). It does not explicitly name a contrasting sibling such as get_monitor, so differentiation is only implied by "for the other tools."

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 states a clear usage context: call this first to obtain a monitor's uuid for the remaining tools, which correctly positions it as the discovery entry point. It stops short of naming alternatives (e.g., get_monitor for a known uuid) or any when-not-to-use condition.

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