Skip to main content
Glama

Pagewatch

by dev.pagelens

register

Create a pagewatch api key for yourself. Free, no signup and no human form. Returns a bearer token that starts with a small free trial so your first read_page, screenshot or pdf works right away. When the trial runs out, hand the returned verification_uri_complete to your human, who confirms one email to unlock 200 more free credits (still free, nothing to pay). Reuse the token by passing it as api_key, or set it as Authorization: Bearer on this server. Nothing is ever charged: pagewatch has no payment processor connected.

    label: a short name for this key, optional.
    purpose: why you want web access, shown to your human on the activation page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
labelNo
purposeNo

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, description fully discloses free nature, no signup, return of bearer token, and activation process. Lacks details on rate limits or multiple calls, but sufficient for registration tool.

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?

Description is somewhat lengthy but each sentence adds value. Front-loaded with main purpose. Could be slightly more concise, but efficient overall.

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?

Given no output schema and simple parameters, description covers tool purpose, return value usage, and activation flow. Adequately complete for its complexity.

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%, but description explains both optional parameters (label and purpose) with clear, meaningful context, compensating for schema gaps.

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 description clearly states the tool creates a pagewatch API key, explains the process, returns a bearer token, and distinguishes from sibling tools like read_page and screenshot.

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?

Provides clear instructions on when to use the tool (first-time registration) and how to proceed after trial runs out. Does not explicitly mention when not to use or alternatives, but context suffices.

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

All Pagewatch toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation5/5

Each tool has a distinct purpose: balance checks credits, pdf converts pages to PDF, read_page extracts markdown, register creates API keys, and screenshot captures images. No overlapping functionality.

Naming Consistency4/5

Tool names are lowercase and descriptive, with 'read_page' using an underscore while others are single words. This minor inconsistency is easy to overlook but prevents a perfect score.

Tool Count5/5

Five tools cover the core needs of a web page tool: key management (balance, register), content extraction (read_page), and output formats (pdf, screenshot). The count is well-scoped for its purpose.

Completeness4/5

The tool set covers key lifecycle and primary page actions. A minor gap is the lack of a tool to delete or manage keys, but balance and register provide sufficient functionality.

Resources