Skip to main content
Glama
Sign In
WPZylos MCP Server

WPZylos MCP Server

Official
by WPDiggerStudio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

i18n_validate

Scan WordPress plugins for internationalization errors including untranslated strings, missing text domains, and incorrect __() calls.

Instructions

Scan plugin for internationalization issues: untranslated user-facing strings, missing text domains, incorrect __() usage, mixed text domains, and translation function best practices.

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": {
      "path": "<path>",
      "textDomain": "<textDomain>"
    },
    "name": "i18n_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesAbsolute path to the plugin root
textDomainYesExpected text domain

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations; description does not disclose read/write nature, side effects, or performance impact beyond stating it scans for issues.

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?

Single sentence with front-loaded purpose; list of issues is slightly lengthy but overall efficient.

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?

Missing output format or return value information; no output schema to compensate, leaving agent without clear expectations.

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 covers 100% with descriptions; description adds context that textDomain is the expected domain, but no additional meaning beyond schema.

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 the tool scans for specific internationalization issues with a list of example checks like untranslated strings and missing text domains, distinct from sibling validation tools.

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

Usage Guidelines3/5

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

Description implies usage for i18n validation of a plugin but provides no explicit guidance on when to use versus alternatives or when not to use.

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