Skip to main content
Glama
fettlesh

fettle-mcp

by fettlesh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

List monitors

list_monitors
Read-onlyIdempotent

Find monitors by name, target, type, status, or tag to retrieve IDs, identify down or degraded services, or find soonest SSL certificate expirations.

Instructions

Find monitors in the organization by name, target, type, status or tag. Each row is short: id, name, type, target, status, is_active, tags, interval_seconds, ssl_expires_at and last_checked_at. Use it first to get a monitor's id, or to answer what is broken now (status ["DOWN", "DEGRADED"]) or which certificates expire first (type ["SSL"], sort ssl_expiry). For one monitor's full settings use get_monitor; for heartbeats use list_heartbeats. Returns a page: items plus total, page, size and pages. An invalid value is a 422 naming the argument. Example: {"status": ["DOWN", "DEGRADED"], "size": 100}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoCase-insensitive substring of the name or the target, up to 255 characters.
tagNoKeep items carrying these tags: a JSON array of up to 10 tags, each up to 50 characters, lowercased before matching. tag_match decides whether all or any of them must match.
pageNoPage number, 1 or more; default 1.
sizeNoRows per page, 1 to 100; default 25. Keep paging until you have seen total rows.
sortNostatus (the default: PENDING, DOWN, DEGRADED, UP, PAUSED, then by name), up_first (healthy first), name, newest, oldest, or ssl_expiry (soonest-expiring certificates first; monitors with no known expiry, non-SSL types or not checked yet, last).
typeNoKeep monitors of any of these types: a JSON array.
statusNoKeep monitors in any of these states: a JSON array. PENDING means no verdict yet.
tag_matchNoall (the default): an item must carry every tag in tag. any: at least one of them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.6.1
    • addedInput schema / properties / page / description
      Added value: +"Page number, 1 or more; default 1."
    • addedInput schema / properties / q / description
      Added value: +"Case-insensitive substring of the name or the target, up to 255 characters."
    • addedInput schema / properties / size / description
      Added value: +"Rows per page, 1 to 100; default 25. Keep paging until you have seen total rows."
    • addedInput schema / properties / sort / description
      Added value: +"status (the default: PENDING, DOWN, DEGRADED, UP, PAUSED, then by name), up_first (healthy first), name, newest, oldest, or ssl_expiry (soonest-expiring certificates first; monitors with no known expiry, non-SSL types or not checked yet, last)."
    • addedInput schema / properties / status / description
      Added value: +"Keep monitors in any of these states: a JSON array. PENDING means no verdict yet."
    • addedInput schema / properties / tag / description
      Added value: +"Keep items carrying these tags: a JSON array of up to 10 tags, each up to 50 characters, lowercased before matching. tag_match decides whether all or any of them must match."
    • addedInput schema / properties / tag_match / description
      Added value: +"all (the default): an item must carry every tag in tag. any: at least one of them."
    • addedInput schema / properties / type / description
      Added value: +"Keep monitors of any of these types: a JSON array."
  2. First observedv0.5.4

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real behavioral context on top: the exact row fields returned, the pagination model (items plus total, page, size, pages), and the 422 error behavior naming the bad argument. It stops short of describing rate limits or ordering guarantees beyond sort, so not a 5.

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?

Front-loaded with purpose, then usage, then return shape, error behavior, and an example — each sentence carries information. The bare field-list enumeration is slightly dense but earns its place given there is no output schema.

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 no output schema, the description compensates by spelling out the returned row fields and the page envelope, and even notes the error shape. For an 8-parameter read tool with rich annotations, 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 already 100%, so baseline is 3. The description still adds cross-parameter meaning the schema lacks: a worked example combining status and size, and the intent mapping (status ['DOWN','DEGRADED'] for outages, type ['SSL'] + sort ssl_expiry for certificates), which helps agents compose parameters correctly.

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 and resource ('Find monitors in the organization') plus the filterable dimensions, and explicitly contrasts itself with siblings get_monitor and list_heartbeats. An agent can select this over get_monitor without opening either 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?

It gives concrete when-to-use cases ('use it first to get a monitor's id', 'answer what is broken now', 'which certificates expire first') and names the alternatives plus the condition that selects them (full settings vs. heartbeats). Exclusions are explicit.

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

Deploy Server

Other Tools