Skip to main content
Glama

build_from_blueprint

Generate a complete WPZylos plugin from a blueprint specification, producing all files: models, migrations, controllers, routes, providers, views, and config.

Instructions

Generate an ENTIRE WPZylos plugin from a comprehensive blueprint specification. Produces all files: entry, bootstrap, PluginContext, models, controllers, migrations, routes, providers, views, and config. The ultimate one-shot generation tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesPlugin name (e.g., "WP Contact Manager")
slugYesPlugin slug (e.g., "wp-contact-manager")
namespaceYesRoot PHP namespace (e.g., "WPContactManager")
prefixYesHook/option prefix (e.g., "wpcm")
textDomainYesText domain (e.g., "wp-contact-manager")
descriptionNoPlugin description
authorNoAuthor name
modelsNoDatabase models to generate
migrationsNoDatabase migrations to generate
controllersNoControllers to generate
providersNoService provider names (e.g., ["AppServiceProvider", "RouteServiceProvider"])
routesNoRoute definitions
adminPagesNoAdmin pages to register
Behavior2/5

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

With no annotations, the description carries full burden. It lists output files but omits important behavioral details such as overwrite behavior, prerequisites, validation, or side effects.

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?

Two sentences that are front-loaded with the action and scope. No redundant words; every sentence adds value.

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 13 complex parameters including nested objects and no output schema, the description does not explain how the blueprint relates to the input parameters or provide guidance on preparing the input. More context is needed for such a powerful tool.

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 baseline is 3. The description adds no extra parameter information beyond what the schema provides.

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?

Description clearly states it generates an entire plugin from a blueprint specification, listing all produced file types. It distinguishes itself from sibling generate_* and scaffold_* tools by being the 'ultimate one-shot generation tool'.

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?

Implies use when a comprehensive blueprint is available and a full plugin is needed, contrasting with smaller-scope siblings. However, it does not explicitly state when to avoid it or provide direct comparisons.

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