Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: Wp php info

wordpress_specialist_wp_php_info
Read-only

Retrieve a curated PHP configuration snapshot for a WordPress site, including extensions, ini settings, disabled functions, and opcache state as structured JSON instead of a full phpinfo HTML dump.

Instructions

[UNIFIED] Curated PHP configuration snapshot — sorted extension list, common ini settings (memory/upload/session/error), disabled functions, opcache state. Returns structured JSON, not the full phpinfo() HTML dump (which would leak server internals). Requires Airano MCP Bridge v2.12.0+ and manage_options.

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": {
      "site": "<site>"
    },
    "name": "wordpress_specialist_wp_php_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

B3.4/5.0
Behavior4/5

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

Goes meaningfully beyond the readOnlyHint annotation: it discloses that the return is curated structured JSON rather than the raw phpinfo() HTML (with the security rationale), and states hard prerequisites — Airano MCP Bridge v2.12.0+ and manage_options capability. It doesn't cover rate limits or what happens if the bridge version is too old.

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?

Front-loaded with the resource and its contents, then the output-format caveat, then requirements — a sensible information hierarchy with no filler. The bracketed [UNIFIED] tag is noise, but it is a single token.

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

Completeness3/5

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

For a one-parameter read-only tool with no output schema, the description covers output shape and access prerequisites well. The unresolved 'site' parameter semantics and the absence of any fallback behavior leave a real gap for a required argument.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter 'site' has 0% schema description coverage, and the description never mentions it or its accepted format (ID, URL, or alias). With only one parameter the gap is partly mitigated by the multi-site context, but the description does nothing to compensate for the schema's silence.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names the specific resource (PHP configuration snapshot) and enumerates its contents — sorted extension list, ini settings, disabled functions, opcache state — so an agent immediately knows this is a PHP-environment read, distinct from the system-level sibling. It stops short of naming which sibling to use instead for non-PHP diagnostics.

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?

Usage is implied rather than stated: the agent must infer this is the diagnostic tool for PHP-level diagnostics (as opposed to system-level). There is no explicit when-to-use / when-not-to-use framing, and no mention of wordpress_specialist_wp_system_info as the contrasting option.

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