Skip to main content
Glama
Sign In
WPZylos MCP Server

WPZylos MCP Server

Official
by WPDiggerStudio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

generate_shortcode

Generate a complete WordPress shortcode class including a render method, based on your plugin's root namespace and class name.

Instructions

Generate a Shortcode class with render method.

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": {
      "rootNamespace": "<rootNamespace>",
      "className": "<className>"
    },
    "name": "generate_shortcode"
  }
}

Input Schema

NameRequiredDescriptionDefault
rootNamespaceYesPlugin root namespace (e.g., "MyPlugin")
classNameYesClass name (e.g., "ShortcodesExample")
extraTokensNoAdditional token replacements

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations available, the description should disclose behavioral traits. It only states the output (class with render method) but omits side effects like file creation, naming conventions, or potential overwrites. This is insufficient for a code generation tool.

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 description is a single sentence with no extra words, making it efficient. However, it lacks structure and could benefit from clearer separation of concerns.

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?

Given the complexity of code generation and the lack of an output schema, the description is too minimal. It does not explain how to use the generated class, what the render method does, or any integration steps.

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% with descriptions for all three parameters. The tool description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

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 that the tool generates a Shortcode class with a render method. It is specific to shortcode generation, distinguishing it from other code generation tools like generate_command or generate_controller.

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?

No guidance is provided on when to use this tool versus the many other generate_* tools. The description does not mention context, prerequisites, or alternatives.

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

Deploy Server

Other Tools