Skip to main content
Glama
Sign In
Proofpage MCP Server

Proofpage MCP Server

by Mehxeo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

proofpage_schedule_source

Schedule or pause recurring captures of a configured web source after authorization by setting an interval; zero pauses, and positive intervals set frequency while the server runs.

Instructions

Schedule a configured web source after user authorization. interval_seconds=0 pauses; otherwise 300 to 31536000. Requires the app/server to remain running; respects robots and budgets.

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": {
      "source_id": "<source_id>",
      "interval_seconds": "<interval_seconds>"
    },
    "name": "proofpage_schedule_source"
  }
}

Input Schema

NameRequiredDescriptionDefault
source_idYes
interval_secondsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the operational dependency that the app/server must stay running, that robots and budgets are respected, and the exact valid interval range including the 0=pause convention. It omits what happens if a schedule already exists, failure behavior, and what is returned.

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

Conciseness5/5

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

Three dense sentences, front-loaded with the action and precondition, then the parameter rule, then the runtime constraints. Every sentence adds new information with no restatement of the title.

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-param scheduling tool with no annotations and no output schema, the description covers the semantics needed to invoke it correctly. Gaps remain on response shape and whether scheduling is idempotent/replaces an existing schedule, which matters for a stateful operation.

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 0%, so the description must compensate. It fully specifies interval_seconds (0 pauses, otherwise 300 to 31536000), which is the genuinely non-obvious parameter, but leaves source_id unexplained beyond the implication that it is a configured source from add_source/list_sources.

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 (schedule) on a specific resource (a configured web source), plus a precondition (after user authorization). It is clearly distinct from siblings like add_source or collect, though it never explicitly contrasts itself with ensure_fresh or recheck_source, which also imply periodic freshness.

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?

'After user authorization' establishes when the tool is permissible, and 'interval_seconds=0 pauses' gives an explicit secondary use case. It does not name alternatives (e.g. one-off collect vs. recurring schedule), so an agent must infer that boundary.

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

Deploy Server

Other Tools