Skip to main content
Glama
Sign In

CatchAll

by com.newscatcherapi
OverviewDiscussionsAdmin

Get Monitor Status

get_monitor_status

Get the status history of a monitor.

Use when:

  • You want to see the timeline of a monitor's state changes (e.g. active, disabled, errored) and any related details.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "monitor_id": "<monitor_id>"
    },
    "name": "get_monitor_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyNoCatchAll API key. Optional if provided via x-api-key header or CATCHALL_API_KEY env var.
monitor_idYesThe monitor ID to inspect.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It implies a read-only operation by stating 'get status history' and 'timeline', but it does not explicitly state that no mutations occur, nor does it disclose any error handling, rate limits, or auth specifics beyond what the schema already notes. This is adequate for a simple get, but lacks explicit safety disclosure.

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?

The description is two sentences long, with the core purpose front-loaded and the 'Use when' guidance immediately following. Every word earns its place; there is no fluff or redundancy.

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 is present (though not shown), so the description need not explain return format. For a simple read tool with one required parameter, the description covers the purpose and usage scenario adequately. It does not mention pagination or limits, but given the simplicity, this is a minor gap.

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 both api_key and monitor_id having clear descriptions. The description adds no additional meaning beyond what the schema provides, so the baseline of 3 applies. It does not elaborate on format or usage nuances.

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 clearly states the tool's function: 'Get the status history of a monitor.' This is a specific verb-resource pair that distinguishes it from other monitor-related tools (list_monitors, enable_monitor, etc.). It even clarifies it provides a timeline of state changes, which is unique.

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 description includes an explicit 'Use when' section that specifies the intended scenario: viewing the timeline of a monitor's state changes. It does not mention alternatives or when not to use, but the context is clear enough for an agent to select this tool over siblings like list_monitor_jobs.

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

All CatchAll toolsInspect
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.

Resources