Skip to main content
Glama
alokemajumder

wpxmcp

by alokemajumder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get ability details

get_ability_info
Read-only

Retrieve a full ability definition, including input and output schemas and destructive status, to understand required parameters and call the ability correctly. Use this to verify structure before executing.

Instructions

Get the full definition of one ability, including its input and output schemas and whether it is destructive, so you can call it correctly the first time. Ability names are namespaced, e.g. "my-plugin/get-site-info".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesFully qualified ability name from discover_abilities, in the form "namespace/ability".
site_idNoWhich configured WordPress site to act on. Optional — with a single site configured it is used automatically; with several, the default site is used unless you name one. Run list_sites for valid ids.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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
    • addedInput schema / properties / name / pattern
      Added value: +"^\\s*[a-zA-Z0-9-]+(?:\\/[a-zA-Z0-9-]+)+\\s*$"
  2. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description does not need to repeat those. The description adds value by specifying that the tool returns input/output schemas and destructive status, which are behavioral traits beyond the read-only nature. This complements the annotations, and there is no contradiction.

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 sentence with no wasted words. It front-loads the primary benefit ('full definition'), then lists the key returned details, and ends with crucial naming guidance. Every clause earns its place.

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?

Given the tool's simplicity (2 params, 1 required, no output schema), the description is adequate. It explains the purpose, the main use case (calling correctly), and the namespacing requirement. It could mention that the output schema is not provided here, but the description already says it returns schemas, so an agent knows to look at the result. Overall, sufficient for correct invocation.

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

Parameters4/5

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

Schema description coverage is 100%, so the schema already explains both parameters. The description adds nuance by noting ability names are namespaced with an example ('my-plugin/get-site-info'), which reinforces the schema's pattern and helps agents format the parameter correctly. This is a small but meaningful addition beyond the schema.

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?

The description clearly states the tool's purpose: 'Get the full definition of one ability, including its input and output schemas and whether it is destructive.' It specifies the resource (an ability) and the exact information it returns. While it doesn't explicitly distinguish itself from siblings, the unusual 'ability' concept makes it unique enough, and it references 'discover_abilities' for context, aiding differentiation.

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 implies that the tool is the prerequisite for calling abilities correctly: 'so you can call it correctly the first time.' It also implies it should be used after discovering abilities. However, it does not explicitly state when NOT to use it or name alternatives, but given the unique purpose, this is acceptable.

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