Skip to main content
Glama

searchnapply

List my job monitors

monitor_list
Read-onlyIdempotent

Purpose: List every one of the user's saved monitors with their counts, in the order they come back. When: Before choosing or changing a saved monitor, to find the one the user means. Cost: About 140 tokens per monitor.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
monitorsYesEvery saved monitor of the user.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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 closed-world behavior, so the description's added value is the cost signal ("About 140 tokens per monitor") and the ordering caveat ("in the order they come back"), both of which the agent cannot infer from structured fields. It does not mention whether results are truncated for large monitor sets, which would have earned 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.

Conciseness5/5

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

Three labeled lines (Purpose / When / Cost) front-load the essential information with no filler sentences. Every line contributes distinct information the agent needs.

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?

An output schema exists, so return values need not be spelled out, and the cost note covers the main practical concern for a no-parameter list call. The only missing piece is any statement about behavior with very large monitor sets or result limits.

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 zero parameters and the schema is fully described, so the baseline of 4 applies. There is no parameter behavior left for the description to clarify.

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 every one of the user's saved monitors") plus a scope qualifier ("every one") and a return-content hint ("with their counts"). It implicitly separates itself from monitor_get by emphasizing enumeration of all monitors, but it never names a sibling tool, so it falls just short of a 5.

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?

The "When" line gives a concrete trigger: before choosing or changing a saved monitor, to identify the one the user means. That effectively routes the agent to this tool ahead of monitor_get, monitor_update, or monitor_delete, though those alternatives are not named explicitly and no when-not condition is stated.

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