Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: Wp permalinks get

wordpress_specialist_wp_permalinks_get
Read-only

Reads the current WordPress permalink structure plus category and tag base prefixes to verify URL settings before making changes.

Instructions

[UNIFIED] Read the current permalink structure (option permalink_structure) plus the category_base + tag_base prefixes. Empty string in structure means "plain" permalinks (?p=N). Requires Airano MCP Bridge v2.16.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_permalinks_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A3.6/5.0
Behavior4/5

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

Beyond readOnlyHint=true, the description discloses two real behavioral facts an agent could not get from annotations: a minimum bridge version (v2.16.0+) and the manage_options capability requirement. It also pre-empts a confusing return case by explaining that an empty structure string means plain ?p=N permalinks.

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?

Three short sentences, each carrying distinct information: what is read, how to interpret an edge-case value, and what prerequisites apply. No repetition of the title and no filler.

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

Completeness4/5

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

With no output schema, the description does the necessary work of naming the returned fields and decoding the empty-string case, which is the main interpretive pitfall. The one remaining hole is the unexplained 'site' parameter, which is required yet undocumented anywhere.

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?

Schema description coverage is 0% and the single parameter 'site' is never mentioned in the description, so there is no added meaning about what a site identifier looks like or how to obtain it. The return-field explanation is useful but belongs to transparency, not parameter semantics.

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?

States a specific verb ('Read') and resource ('current permalink structure') and enumerates exactly what comes back: permalink_structure, category_base and tag_base. It does not explicitly name wp_permalinks_set as its write counterpart, but the get/set naming pair makes the boundary obvious.

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 only implied by the read verb and the manage_options requirement; there is no explicit 'use this before calling wp_permalinks_set' or any statement of when this tool is preferable to wp_option_get for the same option. Adequate but leaves routing to inference.

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