Skip to main content
Glama
NewsCatcher MCP

NewsCatcher MCP

Official

Create a monitor

create_monitor

Set up scheduled monitoring of research runs or companies and receive only new developments on each run. Read results with get_monitor_updates.

Instructions

Watch for new developments on a schedule and get only what is new each run. Three ways: (1) from_run_id: "monitor this" for a finished research run (an events dataset is re-run for new rows; a company run becomes a company monitor); (2) companies or company_list_id: new stories about those companies, optionally only those matching query (e.g. "funding, M&A, executive changes"); the default schedule is daily 09:00 UTC. Read deliveries with get_monitor_updates. Monitors are billed per run or per company (see the pricing docs); empty runs are 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": "create_monitor"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoMonitor name.
queryNoCompany monitors: only stories about this. Dataset monitors: the research request (default: the run's query).
run_nowNoAlso run it right away (within ~5 minutes) instead of waiting for the schedule.
scheduleNoWhen it runs (default daily at 09:00 UTC; weekly for standard/max datasets).
companiesNoCompanies by domain.
from_run_idNoA succeeded research run to keep updated.
company_list_idNoA saved company list; the monitor follows changes to the list.
include_market_activityNoCompany monitors: also stock moves and analyst ratings (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Adds substantial context beyond the annotations: recurring scheduling, default daily 09:00 UTC, billing per run/company with empty runs free, and that a company run becomes a company monitor. It does not describe the returned object, but no output schema exists and the generic safety profile is already covered by the annotations (readOnlyHint=false, destructiveHint=false).

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?

Dense but front-loaded: the behavior comes first, then the three modes, then billing. It is a large block for a single paragraph and repeats the 09:00 UTC default that is already in the schema, but every other sentence carries unique, decision-relevant information.

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 complex, open-world, 8-parameter creation tool with no output schema, the description covers the important modes, scheduling, billing, and the read path. The gaps (return shape, modification via update_monitor) are minor given the annotations and the fully documented schema.

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 100%, so the baseline is 3; the description still adds value by explaining that query means different things for company vs dataset monitors, giving a concrete query example, and clarifying the from_run_id transformation. Some of the default-schedule detail merely repeats the schema, keeping it below 5.

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?

States clearly the resource and behavior (watch for new developments on a schedule, returning only new rows each run) and enumerates the three creation paths (from_run_id, companies, company_list_id). It also distinguishes the read path by naming get_monitor_updates, so an agent can tell this apart from siblings without opening schemas.

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?

Gives explicit guidance on which parameter to use for each of three modes and names the downstream tool for reading deliveries. It does not say when NOT to use this (e.g., use update_monitor to modify an existing monitor vs create a new one), which is the only missing piece.

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