Skip to main content
Glama
NewsCatcher MCP

NewsCatcher MCP

Official

Get monitors

get_monitor
Read-onlyIdempotent

Retrieve a monitor’s settings, schedule, state, and recent runs by ID, or list all monitors when no ID is provided.

Instructions

Show one monitor (settings, schedule, state and its recent runs), or with no monitor_id, all your monitors. 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": "get_monitor"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNotext
monitor_idNoThe monitor; leave out to list all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and openWorld, so safety is covered; the description adds that the call is "Free" (no cost/credit) and that returned data includes recent runs. The word "recent" usefully signals that run history may be truncated, which the agent would otherwise not know. It does not state limits on how many monitors a listing returns.

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?

A single sentence, front-loaded with the primary mode and then the fallback mode, with the cost note at the end. Every clause carries information; nothing is padded.

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 simple read tool with annotations covering safety and no output schema, the description is nearly complete: both invocation modes and the returned content are stated. The only omission is the output format switch, which is minor for this complexity.

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 coverage is 50%: monitor_id is already documented in the schema ("The monitor; leave out to list all."), and the description mostly restates that behavior. The format parameter (text/json) is not mentioned in either place, so the description does not compensate for the coverage gap. Baseline 3 is appropriate.

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 uses a specific verb ("Show") and resource ("monitor") and spells out what is returned: settings, schedule, state and recent runs. It also distinguishes the two modes (one monitor vs. all monitors), so an agent can tell exactly what it fetches. It stops short of naming related siblings such as get_monitor_updates for full run history.

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 gives a clear selection rule: pass a monitor_id to inspect one monitor, omit it to list all. That covers the primary when-to-use decision for this tool. It does not name alternatives or exclusions (e.g., when to prefer get_monitor_updates), leaving that inference to the agent.

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