Skip to main content
Glama

OnPage.dev

by dev.onpage
OverviewDiscussionsAdmin

Plan the work

plan
Read-onlyIdempotent

Plans for migrations, experiments and the team. Pick with mode: redirects = Redirect map for a migration or URL change. split_test = SEO split test on a page template, with the Worker. Needs urls, field, pattern. sprint = Fixes into a week plan of tickets per role. Needs fixes[{title, url, detail, severity, impact, effort}].

Input Schema

NameRequiredDescriptionDefault
modeNoDefault redirects.
urlsNoPages of one template.
fieldNoWhat to change.
fixesNo
hoursNoHours per week per role, default 8 each.
weeksNoWeeks to plan, default 4.
clicksNoOptional clicks per page for a balanced split.
detailNobrief = short summary.
formatNoOutput format, default redirects (Cloudflare Pages and Netlify).
patternNoThe new value with {title} or {description} as placeholders.
new_siteNoNew site address, to read its sitemap instead of new_urls.
new_urlsNo
old_siteNoOld site address, to read its sitemap instead of old_urls.
old_urlsNo
memory_keyNosite_memory key, records this call.
start_dateNoOptional planned start, YYYY-MM-DD.

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. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, so safety is covered. The description adds mode-specific behavioral context the annotations cannot: what each mode produces (redirect map, Worker-based split test, week plan of tickets per role) and the required input shapes, which is genuine added value.

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 mode breakdown is front-loaded right after a one-line purpose statement, and each clause carries distinct information. It is dense shorthand rather than filler, though the compact "=" notation reads a little run-on.

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?

For a 16-parameter, multi-mode tool, the description covers the three modes' key inputs and the output schema handles returns. However, it leaves many parameters (hours, weeks, detail, format, old_site/new_site, clicks, memory_key, start_date) unmapped to modes, so an agent must infer which apply when.

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?

With 81% schema coverage the baseline is 3, but the description goes further by mapping parameters to modes (split_test needs urls/field/pattern; sprint needs fixes with its subfields), which the schema alone cannot express since param applicability is mode-dependent.

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?

The description names the verb ("Plans") and the three concrete resources/use cases (migrations, split tests, team sprints), then breaks each mode down so an agent can tell redirects from split_test from sprint. It is specific and non-tautological, though it does not differentiate from any sibling tool by name.

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?

It explicitly tells the agent how to select behavior via "Pick with mode" and gives a condition/purpose for each of the three modes, plus the inputs each mode needs. There is no "when not to use" guidance or pointer to alternative sibling tools, keeping it out of the top band.

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