Skip to main content
Glama

scaffold_plugin

Generates a complete WPZylos plugin scaffolding with all required files and directory structure, enabling rapid development.

Instructions

Generate a complete new WPZylos plugin with all required files: entry file, bootstrap, PluginContext, Activator, Deactivator, Uninstaller, composer.json, config files, and directory structure. Based on the wpzylos-scaffold template.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesPlugin name (e.g., "WP Testimonials")
slugYesPlugin slug (e.g., "wp-testimonials")
namespaceYesRoot PHP namespace (e.g., "WPTestimonials")
prefixYesHook/option prefix (e.g., "wpt")
textDomainYesText domain (e.g., "wp-testimonials")
descriptionNoPlugin description
authorNoAuthor name
authorUriNoAuthor website
minPhpNoMinimum PHP version (default: 8.1)
minWpNoMinimum WordPress version (default: 6.0)
Behavior2/5

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

With no annotations, the description carries full burden but only lists generated files without disclosing side effects like overwriting behavior, required permissions, or any destructive actions.

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?

The description is a single, well-structured sentence that immediately conveys the tool's purpose and outputs, with no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite many parameters and no output schema, the description lacks context on prerequisites, post-generation steps, or how the generated plugin integrates, leaving significant gaps for an agent.

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 the schema already documents all parameters. The description adds no additional insight beyond what the schema provides, resulting in a baseline score of 3.

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 generates a complete new WPZylos plugin and lists specific files, distinguishing it from sibling tools that scaffold individual components.

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?

The description does not provide any guidance on when to use this tool versus alternatives, nor does it mention prerequisites or scenarios where it should be avoided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/WPDiggerStudio/wpzylos-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server