Skip to main content
Glama
Sign In
WordPress Plugin Directory MCP Server

WordPress Plugin Directory MCP Server

by juanma-wp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

read_plugin_file

Retrieve the contents of any file inside a WordPress plugin by providing the plugin slug and the relative file path.

Instructions

Read the contents of a specific file from an extracted plugin

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": {
      "slug": "<slug>",
      "file_path": "<file_path>"
    },
    "name": "read_plugin_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesPlugin slug
file_pathYesRelative path to the file within the plugin

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.5

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description should disclose behavioral traits like read-only nature, error handling (e.g., file not found), or size limits, but only states 'Read the contents'.

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, efficient sentence with no wasted words, making it highly concise and easy to parse.

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?

The description omits key context: the necessity of prior plugin extraction, the output format (e.g., raw text), and error behavior, leaving the agent underinformed.

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 provides clear descriptions for both parameters ('Plugin slug' and 'Relative path'), and the tool description adds no extra meaning beyond that.

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 action 'Read the contents' and the resource 'a specific file from an extracted plugin', distinguishing it from sibling tools that list files, compare plugins, or get plugin info.

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 offers no guidance on when to use this tool versus alternatives, nor does it mention prerequisites like the plugin needing to be extracted first.

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