Skip to main content
Glama
eMCP for Evolution CMS

eMCP for Evolution CMS

Official

Content Tree Tool

evo.content.tree
Read-only

List visible documents under a CMS page or site root, ordered by parent, menu index and ID, with depth and menu index range filters to map content trees.

Instructions

List visible documents below a document or the site root, ordered by parent, menuindex and id. Use depth 1 for direct children and menuindex ranges. Use evo.content.ancestors to walk up or evo.content.siblings for documents under the same parent.

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": {
      "id": "<id>",
      "limit": "<limit>"
    },
    "name": "evo.content.tree"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesDocument ID, or 0 for the virtual site root.
depthNoLevels below the anchor, up to the configured maximum. At 0, depth 1 returns top-level documents.
limitYesMaximum items to return, up to the configured server limit.
offsetNoNumber of matching records to skip after sorting.
with_tvsNoTV names to return under tvs. Append :d to a name to fall back to its default value.
menuindex_toNoInclusive upper menuindex bound, only at depth 1.
menuindex_fromNoInclusive lower menuindex bound, only at depth 1.

Output Schema

NameRequiredDescriptionDefault
metaYes
itemsYesReturned records in the order defined by the tool. Empty when there are no matches.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description carries the rest, and it does add real context: results are limited to 'visible' documents (permission filtering), output is deterministically ordered by parent, menuindex and id, and menuindex bounds only apply at depth 1. It stops short of describing pagination behavior or what the maximum depth/limit ceilings actually are, which are left to the schema.

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, each doing distinct work: what it returns and how it is ordered, the depth/menuindex hint, then sibling routing. The core capability is front-loaded and there is no filler.

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?

An output schema exists and the input schema is fully described, so the description need not cover return values or parameter syntax. What structure cannot express — visibility filtering, deterministic ordering, and when to pick a sibling tool instead — is all present, making this complete for a read-only listing tool.

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?

Schema description coverage is 100%, so the parameters are already fully documented, and the description mostly restates the depth-1 semantics that the schema itself explains. The only genuinely additive hint is linking depth 1 to menuindex range usage, which is marginal beyond structured data. Baseline 3 applies.

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?

States a specific verb and resource ('List visible documents') plus the anchor scope ('below a document or the site root') and the sort order ('parent, menuindex and id'). It also names the two closest siblings it is not, so an agent can separate tree listing from upward traversal and same-parent listing without opening a schema.

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

Usage Guidelines5/5

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

Gives positive routing rules ('Use depth 1 for direct children and menuindex ranges') and explicit alternatives ('Use evo.content.ancestors to walk up or evo.content.siblings for documents under the same parent'). The condition that selects each alternative is stated rather than inferred.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.