Skip to main content
Glama
Sign In

pageaudit

by online.pageaudit
OverviewDiscussionsAdmin

Configure domain monitor

configure_domain_monitor
DestructiveIdempotent

Requires the account session, current X-Organization-Id and CSRF for writes. Enable or stop domain monitoring, or pause notices for maintenance. Uses existing rights; 402 supplies checkout instructions and never buys automatically. Stopping a monitor does not cancel a subscription. Activation requires a current domain benefit, a preserved prepaid watch benefit or the account trial. Count a registry domain once per account, including its organization copies. Add only the tab's origin. HTTP receives DNS checks only. Stopping monitoring keeps history and does not cancel a subscription. Maintenance pauses notices while collection continues. Confirm enabled, no suspension and next_check_at after saving.

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": {
      "id": "<id>",
      "revision": "<revision>",
      "enabled": "<enabled>",
      "maintenance_until": "<maintenance_until>"
    },
    "name": "configure_domain_monitor"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesOwned tab ID from list_tabs.
enabledYesTrue enables collection; false stops it.
revisionYesCurrent revision from the corresponding settings or monitor. Use zero for the first change.
maintenance_untilYesFuture Unix milliseconds within 30 days, or null.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations, the description discloses authentication requirements, CSRF for writes, the non-purchase behavior on 402, side effects such as preserving history and not canceling subscriptions, maintenance semantics, and post-save checks for enabled, suspension, and next_check_at. This is substantial behavioral context for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description contains useful operational detail, but it is long and repetitive: the point that stopping does not cancel a subscription appears twice in near-identical language. It also opens with session/CSRF prerequisites before stating the core action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex mutation tool with rich annotations and full schema coverage, the description is complete enough to call correctly. It covers prerequisites, activation constraints, side effects, maintenance behavior, and post-save verification even though no output schema exists.

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 already 100%, so the schema documents all four parameters. The description adds some meaning for enabled and maintenance behavior, but does not materially clarify id or revision beyond what the schema already states.

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 states specific actions: enable or stop domain monitoring and pause notices for maintenance. It distinguishes this tool's scope from related domain/DNS operations by explaining that HTTP receives DNS checks only and that stopping a monitor does not cancel a subscription.

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 gives clear context for when this operation is used: enabling collection, stopping it, or pausing notices for maintenance. It includes activation prerequisites and notes that 402 provides checkout instructions, but it does not explicitly name sibling alternatives or when-not-to-use conditions.

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

All pageaudit 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