Skip to main content
Glama

OnPage.dev

by dev.onpage
OverviewDiscussionsAdmin

Cloudflare Workers

edge_worker
Read-onlyIdempotent

Fixes applied at the edge on the user's own Cloudflare, on any CMS. Pick with mode: rules = One Worker that fixes a whole section by rules. Needs audit_id. prerender = Serve rendered HTML to AI crawlers for JavaScript apps. Needs url.

Input Schema

NameRequiredDescriptionDefault
urlNoA page of the app, for example https://app.example.com/pricing.
modeNoDefault rules.
detailNobrief = short summary.
audit_idNoId of a completed site audit (start_site_audit, then get_site_audit until complete).
site_nameNoBrand name for title endings, for example 'Acme Shoes'.
memory_keyNosite_memory key, records this call.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedOutput schema / description
      Removed value: -"The result as structured data; fields depend on mode."
  2. Changed2 schema fields changed
    • changedInput schema / properties / detail / description
      Previous value: -"brief returns a short summary, default full."New value: +"brief = short summary."
    • changedInput schema / properties / memory_key / description
      Previous value: -"Optional site_memory key, to record this call in the site memory."New value: +"site_memory key, records this call."
  3. Changed1 schema field changed
    • addedInput schema / properties / detail
      Added value: +{
+  "description": "brief returns a short summary, default full.",
+  "enum": [
+    "full",
+    "brief"
+  ],
+  "type": "string"
+}
  4. Changed1 schema field changed
    • addedInput schema / properties / memory_key
      Added value: +{
+  "description": "Optional site_memory key, to record this call in the site memory.",
+  "maxLength": 80,
+  "type": "string"
+}
  5. Added

TDQS

B3.2/5.0
Behavior1/5

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

The description says 'Fixes applied at the edge on the user's own Cloudflare', which describes a mutating deployment to the user's Cloudflare account, while annotations declare readOnlyHint=true and destructiveHint=false. A write action presented as read-only is the exact contradiction pattern to flag. It also omits the auth/permission requirements such a deployment would need.

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?

Front-loaded with what the tool is, then mode-by-mode detail and prerequisites in three tight sentences; every clause carries information. The telegraphic 'Pick with mode:' / 'Needs audit_id.' style is slightly clipped but wastes nothing.

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?

An output schema exists, so return values need not be explained, and the two modes plus their prerequisites are covered. However, for an openWorld tool that touches the user's own Cloudflare, the description never states the authorization/setup prerequisite, what exactly is deployed, or whether it can be undone, leaving meaningful gaps.

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 coverage is 100%, so the baseline is 3, and the schema already documents url, mode, detail, audit_id, site_name and memory_key. The description does add one piece of meaning beyond the schema: the conditional requirement that rules needs audit_id and prerender needs url, which the flat schema does not express.

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 resource (a Worker running on the user's own Cloudflare, CMS-agnostic) and splits it into two named modes, rules and prerender, with a one-line definition of each. An agent can tell what the tool produces, though no sibling tool is named to differentiate it from the many other fix/asset generators in the suite.

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 clear mode-selection guidance and the prerequisite for each mode: 'rules ... Needs audit_id' and 'prerender ... Needs url'. That is actionable when-to-use context, but it never says when to prefer edge_worker over siblings such as llms_txt, robots_txt, or get_fix_pack, so it stops short of full routing guidance.

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

All OnPage.dev toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources