Skip to main content
Glama

Personalized Domain Monitor

monitor
Destructive

Manage cross-platform domain monitoring tasks that track changes in WHOIS, DNS, and host-supplied page content. Data is encrypted at rest (AES-256-GCM) in a private per-user directory.

Actions:

  • get: retrieve monitors and check eligible WHOIS/DNS targets, returning current and previous data with change flags.

  • set: create a monitor, subject to the account tier's maximum.

  • update: save host-supplied page, WHOIS, or DNS state for a monitor.

  • delete: remove a monitor.

  • history: list the changes actually observed over time, optionally for one domain. get compares against the previous check only; history answers when a domain changed and what it changed from.

Requires a registered account with memory enabled.

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

Input Schema

NameRequiredDescriptionDefault
idNoMonitor task ID (update and delete)
dnsNoDNS result, backward compatibility (update only)
daysNohistory only: how far back to look, in days. Default 30, maximum 365.
noteNoWhat to watch for: the user's intent in natural language (set only)
pageNoPage content summary from web_fetch (update only)
toolsNoComma-separated: whois, dns, web_fetch. Default: whois,dns (set only)
whoisNoWHOIS result, backward compatibility (update only)
actionNo'get', 'set', 'update', 'delete', or 'history'. Defaults to 'get' if not specified.
domainNoDomain to monitor (set; also optional on history to filter to one domain)

Output Schema

NameRequiredDescriptionDefault
errorNoError message when success is false
totalNoNumber of active monitors (get only)
messageNoHuman-readable result message
monitorNoCreated monitor details (set only)
successNoWhether the request was successful
monitorsNoList of monitors with auto-check results (get only)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedOutput schema / required
      Removed value: -[
      -  "success"
      -]
  2. Changed1 schema field changed
    • changedInput schema / properties / note / description
      Previous value: -"What to watch for — user's intent in natural language (set only)"New value: +"What to watch for: the user's intent in natural language (set only)"
  3. Changed3 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"'get', 'set', 'update', or 'delete'. Defaults to 'get' if not specified."New value: +"'get', 'set', 'update', 'delete', or 'history'. Defaults to 'get' if not specified."
    • addedInput schema / properties / days
      Added value: +{
      +  "description": "history only: how far back to look, in days. Default 30, maximum 365.",
      +  "type": "string"
      +}
    • changedInput schema / properties / domain / description
      Previous value: -"Domain to monitor (set only)"New value: +"Domain to monitor (set; also optional on history to filter to one domain)"
  4. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and non-idempotent, and the description goes beyond them with real prerequisites: a registered account with memory enabled, per-user encrypted storage (AES-256-GCM), and an account-tier cap on how many monitors 'set' can create. It does not state what exactly is lost on delete or how the tier limit is surfaced when exceeded, keeping it below 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.

Conciseness4/5

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

Front-loaded purpose sentence followed by a scannable action list, with the get/history nuance placed inside the relevant action rather than in a trailing note. The encryption-at-rest sentence is behavioral rather than selection-critical, but it is one line and not padding.

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?

With nine optional parameters and an output schema present, the description covers the prerequisites, the tier constraint, and the per-action routing that an agent needs to call it correctly. Return-value explanation is rightly omitted because an output schema exists; only the exact consequences of delete remain unstated.

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%, so the baseline is 3; every parameter including action, days, domain, and tools is already documented in the schema. The description adds cross-parameter semantics (that 'domain' filters history, and that 'tools' defaults to whois,dns) but largely restates what the schema already carries.

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 opens with a specific verb+resource ('Manage cross-platform domain monitoring tasks') and names exactly what is tracked: WHOIS, DNS, and host-supplied page content. The enumerated sub-actions (get/set/update/delete/history) make it unmistakable that this is a stateful monitor manager rather than a one-shot lookup like the whois or dns siblings.

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?

Each action is paired with its purpose, and the get-vs-history boundary is spelled out explicitly: 'get compares against the previous check only; history answers when a domain changed and what it changed from.' What's missing is guidance on when to use this tool instead of sibling lookups (whois, dns, domain_changes) for non-monitored queries.

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.