Skip to main content
Glama

Accept a page change

accept_page_change
Idempotent

Makes the page as it is now the new baseline of a monitor with content_watch, after get_website_changes shows a change you or the site's owner made on purpose. Later looks compare with it. Free.

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>"
    },
    "name": "accept_page_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMonitor ID from list_monitors.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare idempotent=true and destructive=false, so safety is partly covered. The description adds real value beyond them by explaining the lasting effect ('later looks compare with it') and the 'Free' billing note, though it does not say whether the previous baseline is discarded or recoverable.

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?

Two short sentences with the core action front-loaded and the prerequisite named second. The phrasing 'Makes the page as it is now the new baseline' is slightly clunky and the trailing 'Free.' is a fragment, but nothing is wasted.

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 one-parameter, non-destructive, idempotent tool with no output schema, the description covers what it does, when to call it, and the downstream consequence. Only the fate of the prior baseline and any auth requirements are left 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?

There is a single required 'id' parameter with 100% schema description coverage pointing to list_monitors. The description adds no syntax or sourcing detail beyond the schema, so the baseline of 3 applies.

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?

Names a specific action and object: it promotes the page's current content to the new baseline for a monitor with content_watch. It also ties the tool to the content-watch workflow, which separates it from generic monitor CRUD siblings, though it never explicitly distinguishes itself from the similar-sounding change_maintenance_occurrence.

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?

Gives a clear trigger: call it after get_website_changes reveals a change that was made deliberately. The phrase 'on purpose' implicitly warns against accepting unintended changes, but no alternative tool is named for the unintended case, so the when-not path is only inferred.

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.

Resources