Skip to main content
Glama
Sign In
Nucleo for WordPress

Nucleo for WordPress

by nucleowp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

nucleo-terms-get

Read-onlyIdempotent

Lists taxonomies managed by the content API, or returns a taxonomy’s terms parent before child with content hashes. Use the hashes as bases when saving to update only terms that changed.

Instructions

Returns the taxonomies the content API manages. With "taxonomy", also returns its terms, parents before children. Each term has a "hash" of its content: pass it as "base" to terms-set, which then saves only if the term did not change since.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nucleo-terms-get"
  }
}

Input Schema

NameRequiredDescriptionDefault
taxonomyNoTaxonomy slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds important behavioral detail beyond that: terms are returned parents before children, and each term includes a hash used for optimistic concurrency when passed as base to nucleo-terms-set.

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 compact and front-loaded, with three short sentences that each add useful information. There is no redundant restatement of the tool name or annotations.

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?

For a one-parameter read tool with no output schema, the description adequately covers the return shape: taxonomies, optional terms, parent-before-child ordering, and per-term hashes. It could additionally mention behavior for an unknown taxonomy slug or any pagination limits, but the core information is present.

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 coverage is 100%, and the schema already labels taxonomy as a taxonomy slug. The description adds meaning by explaining the conditional effect of supplying it and the ordering of returned terms, which the schema alone does not convey.

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 specific read operation: it returns taxonomies, and with the optional taxonomy parameter it also returns that taxonomy's terms. This is clear enough for an agent to distinguish it from related term tools such as nucleo-terms-set.

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 explains the key conditional usage: omit taxonomy to list taxonomies, or supply taxonomy to retrieve its terms. It also hands off the term hash to nucleo-terms-set as base for conditional saving, giving clear context without exhaustively naming exclusions.

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