Skip to main content
Glama
Sign In

pageaudit

by online.pageaudit
OverviewDiscussionsAdmin

Preview domain alerts

preview_domain_alerts

Requires the account session, current X-Organization-Id and CSRF for writes. Review the exact selected domains before changing renewal notices. Does not activate monitors, purchase access or change certificate notice timing. Select up to 25 saved pages. Repeated registrable domains count once. The server checks the account, organization and current revisions again. A stale preview changes nothing. This does not activate monitoring or purchase access.

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": {
      "tabs": "<tabs>",
      "lead_days": "<lead_days>"
    },
    "name": "preview_domain_alerts"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabsYesOne to 25 owned tab IDs.
lead_daysYesDays before domain expiry for renewal notices.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations, the description discloses the auth requirements (account session, X-Organization-Id, CSRF), that the server re-checks account/organization/revisions, and that a stale preview is a safe no-op. That is genuinely useful behavioral context for a non-readOnly, non-idempotent tool. The repeated 'does not activate/purchase' sentences and the confusing 'CSRF for writes' phrasing on an apparently non-mutating preview keep it from 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.

Conciseness3/5

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

It opens with authentication plumbing rather than the tool's purpose, and the non-mutation guarantee is stated twice ('Does not activate monitors, purchase access...' and 'This does not activate monitoring or purchase access'). Several sentences could be merged without losing 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 two-parameter preview with no output schema, the description covers auth preconditions, mutation boundaries, server-side revalidation and stale-data behavior, which is close to what an agent needs. Missing only the explicit hand-off to the apply step.

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, but the description adds real semantics the schema does not: the cap of 25 saved pages and, more importantly, the dedupe rule that repeated registrable domains count once. That materially changes how an agent should construct the tabs array.

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 states a specific action (preview/review the selected domains for renewal notices) and constrains scope clearly. It does not name the sibling tool it pairs with (apply_domain_alerts), so differentiation from that sibling is left to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Review the exact selected domains before changing renewal notices' implies a pre-flight usage, and the description excludes activating monitors, purchasing access and changing certificate notice timing. However, it never explicitly names apply_domain_alerts as the follow-up tool or states when not to preview, leaving routing implied rather than stated.

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