Skip to main content
Glama

Resume monitored page

resume_source
Idempotent

Start monitoring a paused page again — the counterpart to pause_source. Checks restart on the page's normal frequency and spend credits again, one per page read. Calling it on a page that is already monitored is a no-op, reported as alreadyActive. The first check after a long pause compares the page against how it looked when it was paused, so it can report everything that changed in between. The status field reports the page's stored state, not a prediction: on an account with no credits a resume still answers active, and the page then either keeps a weekly check (verified e-mail, page among its first three months on the free rotation) or is parked again as creditPaused when its next check comes due — call get_credit_balance to tell whether checks will actually run.

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": {
      "sourceId": "<sourceId>"
    },
    "name": "resume_source"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceIdYesThe source ID to resume.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the supplied mutation and idempotency annotations, it discloses credit consumption, check frequency, the alreadyActive result, comparison against the paused baseline, and the distinction between stored status and future check execution. It also explains the no-credit and creditPaused outcomes, including the limited free-rotation exception.

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?

The primary action and pause_source relationship are front-loaded, and the sentences generally convey useful operational information. However, the single dense paragraph—especially the lengthy final sentence combining status semantics, credits, and free-rotation conditions—is harder to scan than necessary.

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 one-parameter tool without an output schema, the description covers the important state transitions, idempotent behavior, credit effects, first-check baseline, and reported status values. It gives the agent enough context to invoke the operation and interpret potentially misleading active responses.

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?

The schema already fully documents the sole sourceId parameter, and the description adds no ID format, acquisition method, or validation details. With 100% schema coverage, the baseline score of 3 is appropriate.

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 opening sentence gives a specific action and resource—starting monitoring for a paused page again—and explicitly identifies the tool as the counterpart to pause_source. This clearly distinguishes it from the other source-management siblings.

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

Usage Guidelines5/5

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

It identifies the paused-page use case, explains that invoking it on an already monitored page is a no-op, and directs the agent to get_credit_balance when determining whether checks will actually run. These details provide concrete selection and follow-up guidance.

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