Skip to main content
Glama
Sign In

pageaudit

by online.pageaudit
OverviewDiscussionsAdmin

Watch tab

watch_tab
Destructive

Turns the daily watch on or off for a tab: it re-audits the page once a day and e-mails when the score drops or a new error/warning appears. Needs the signed-in account (its browser session cookie); a guest token gets 403 account_required. When a plan ends, the pages beyond the account's limit pause until the next purchase. With monitor: true the page is re-audited once a day and an e-mail goes out when the score drops or a new error/warning appears — never on an improvement. Watching needs an account (the alert has to reach someone) and each account watches a limited number of pages. When a plan ends, the pages beyond the account's limit pause (the oldest stay) until the next purchase.

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": {
      "guest_token": "<guest_token>",
      "id": "<id>",
      "monitor": "<monitor>"
    },
    "name": "watch_tab"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesID of the tab to change.
monitorYestrue watches, false stops watching
guest_tokenYesguest pa_… — refused: a guest has no e-mail to warn
monitor_emailNowhere the alert goes; empty = account e-mail

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / guest_token / description
      Previous value: -"session sess_… (a guest cannot be warned)"New value: +"guest pa_… — refused: a guest has no e-mail to warn"
  2. Added

TDQS

B3.4/5.0
Behavior4/5

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

Goes meaningfully beyond annotations by disclosing auth requirements (account session cookie, 403 account_required for guests), the alert rule (fires only on score drop or new error/warning, never on improvement), and the plan-limit pausing behavior. Annotations declare destructiveHint=true but give no context on what the mutation touches or is reversible; the description fills in the alerting and quota behavior instead.

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

Conciseness2/5

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

The description is substantially redundant: the first sentence and the 'With monitor: true' clause restate the same daily re-audit and e-mail-on-drop behavior almost verbatim, and the account/plan-limit paragraph is repeated twice. Front-loading is fine, but the repeated content wastes space and hurts readability.

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

Completeness3/5

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

Covers auth, alerting, and quota-pausing behavior for a tool with no output schema, so the essentials are present. It omits what the response looks like after toggling and how monitor_email interacts with account e-mail when both are set, leaving some gaps for a 4-parameter mutation.

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 all four parameters are already documented in the schema. The description reinforces the monitor:true/false semantics and the e-mail outcome but adds no syntax, format, or edge-case detail beyond what the schema provides. Baseline 3 applies when the schema carries the semantics.

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?

States a specific verb and resource: turns the daily watch on or off for a tab, plus the resulting behavior (daily re-audit, e-mail on score drop or new error/warning). It is distinguishable from siblings like list_tabs, run_tab, and tab_history. It does not explicitly contrast itself with a sibling, so it falls short of a 5.

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?

Explains prerequisites well: requires a signed-in account session cookie, and a guest token receives 403 account_required, plus what happens when a plan ends. However, it never names an alternative tool or states when not to use this one, so usage context is implied rather than routed.

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