Skip to main content
Glama
alokemajumder

wpxmcp

by alokemajumder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Save a playbook

save_skill

Save a reusable playbook to define site-specific conventions, client tone, or deployment routines, then load it in future sessions to apply the same rules automatically.

Instructions

Save a playbook so future sessions follow the same conventions — your site's structure, a client's tone of voice, a deployment routine, the fields a particular theme expects. Written to ~/.wpxmcp/skills and loaded by load_skill from then on. Saving a skill with a bundled skill's name overrides it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesLowercase hyphenated identifier, e.g. "acme-blog-conventions".
titleYesHuman-readable title.
contentYesThe playbook itself, in Markdown. Write it for an agent: concrete steps, exact tool names, and the mistakes to avoid.
keywordsNoTerms that should trigger this skill, e.g. ["acme", "blog post", "tone"].
descriptionYesOne line on when this skill applies — this is what load_skill matches against.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.0.0

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the persistence location (~/.wpxmcp/skills), the future-loading behavior, and the important side effect that saving under a bundled skill's name overrides it. This is exactly the kind of behavioral detail an agent needs when deciding whether to call the tool.

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 sentences with no filler. The first sentence conveys purpose and examples, the second explains storage and future loading, and the third warns about the override edge case. Each sentence earns its place.

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

Completeness5/5

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

All five parameters are fully described in the schema, and the description covers the essential behavioral context: where the skill is written, how it is loaded later, and what happens on name collision. No critical information is missing for an agent to use this tool correctly.

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?

The input schema has 100% description coverage, so the schema already documents all five parameters. The tool description adds no meaningful per-parameter semantics beyond that baseline.

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 states a concrete verb-resource pair ('Save a playbook') and clearly explains the purpose: making future sessions follow the same conventions. It also differentiates the tool from load_skill by explaining that saved skills are later loaded by load_skill.

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

Usage Guidelines4/5

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

The description gives clear context for when to use this tool: when you want to persist conventions like site structure, client tone, or deployment routines. It references load_skill as the counterpart, providing a useful routing cue, though it does not explicitly contrast with delete_skill or list_skills.

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