Connect Croma first: MCP server. A monitor created from an
agent is the same monitor the API and the console at
platform.usecroma.com/monitors manage.
Ask for it
Say what to watch, where, and who should hear about it. For example:- “Avísame cuando la ANM publique algo sobre el título AD9-111. Envíalo a legal@empresa.com.”
- “Watch SECOP II for new contracts with NIT 900123456 and email me every Monday at 8.”
- “Alert me when the Corte Constitucional publishes a ruling on habeas data, only the ones about tutela.”
- “Pause my AD9-111 monitor.” / “What did my monitors find this week?”
What the agent does
1
Searches the source
It runs the search with your filters, for example
anm_notices_search with
title_number: "AD9-111", so you see what exists today.2
Creates the monitor
It calls
create_monitor with endpoint set to that search’s tool name and
query set to the same arguments. The schedule defaults to right after the
source’s own refresh.3
Asks for the recipients
Up to three addresses. It never guesses one; if you did not give them, it asks.
4
Runs the baseline
The first run records what already matches and sends a welcome email. From
then on, every email carries only what is new.
The tools
endpoint takes the tool name (anm_notices_search), the catalog id
(anm-notices-search) or the path (/co/anm/notices-search/v1). The searches a
monitor can watch are listed in Monitorable sources.
Tips
- Be exact about what to watch. An identifier (a placa, a NIT, a radicado) makes a precise monitor; free text works too and matches more.
- Say “only when there is something new” to skip the short “nothing new”
email; the agent sets
notify: "on_new". - Describe what counts (“only notices about caducidad”) and the agent adds a relevance filter. Discarded rows stay in the monitor.
- Each run spends one credit. Creating and managing monitors is free.
- Clients that load tools on demand, like Claude, find these tools when they
search for “monitor” or “alert”. If yours does not, ask it to use
create_monitor.