Skip to main content
Glama
Sign In

Paladin Front PHP Rescue & Zero-PHP Migration MCP

by io.github.AGI-CEO
OverviewDiscussionsAdmin

convert_php_site_to_nextjs

Scrapes a target WordPress or PHP website, extracts business branding, headings, services, and photos, and compiles a hardened, zero-PHP Next.js App Router live preview with Stripe claim integration.

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": {
      "url": "<url>"
    },
    "name": "convert_php_site_to_nextjs"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesTarget WordPress/PHP website URL to scrape and convert into a hardened, zero-PHP Next.js App Router preview.
abVariantNoOptional A/B testing paywall variant for the converted preview.A

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the output artifact (a live preview) and mentions hardening and Stripe claim integration, which is real behavioral context. However it omits side effects (does it publish/deploy?), expected duration for a full-site scrape, auth requirements, and any rate or cost constraints.

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?

A single front-loaded sentence led by the primary verb 'Scrapes', with no filler or repetition. It is dense with many clauses, but each clause conveys a distinct stage of the pipeline, so little is wasted.

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?

There is no output schema and no annotations, so the description must carry the operational picture. It explains what is produced but not how the preview is accessed, how long it persists, whether the source site is modified, or failure modes — meaningful gaps for a multi-stage scrape-and-build operation.

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 description coverage is 100%, so both url and abVariant are already documented in the schema, including the enum. The description adds no syntax, format, or behavioral detail beyond restating the conversion target, so the baseline of 3 applies.

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 names specific verbs and resources in sequence (scrapes, extracts branding/headings/services/photos, compiles a zero-PHP Next.js App Router preview) and includes a distinctive extra (Stripe claim integration). This is clearly distinguishable from the sibling scan/remediation tools, which do not convert anything.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no reference to the siblings scan_php_vulnerability or get_php2shell_remediation_guide. An agent cannot tell from the text whether this should follow a scan, whether the target site must be PHP/WordPress specifically, or what triggers use.

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

All Paladin Front PHP Rescue & Zero-PHP Migration MCP toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources