eMCP for Evolution CMS

Official

Overview Schema Source Related Servers Discussions Admin

Content Prev Siblings Tool

evo.content.prev_siblings

Read-only

Retrieves previous sibling content nodes under the same parent by lower menuindex, helping you inspect or navigate adjacent items in Evolution CMS.

Instructions

Read previous siblings of a content node (lower menuindex in 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.prev_siblings"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`limit`	Yes
`offset`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds real behavioral context by defining the ordering rule (lower menuindex within the same parent), which is not derivable from the name. However, it says nothing about pagination behavior or result ordering/shape despite having limit and offset parameters.

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?

A single tight sentence with the core operation front-loaded and the disambiguating clause immediately after. No wasted words and nothing buried.

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

Completeness2/5

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

For a read-only list tool with three undocumented parameters, no output schema, and required pagination inputs, the description is too thin. An agent can guess intent but not how to page, whether limit is a hard cap, or what ordering the results arrive in.

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%, so the description carries the full burden for three parameters, yet it never explains id (presumably the content node), limit (required, unusual for a list call), or offset. The phrase 'content node' hints at the id's meaning but leaves limit/offset and their interaction completely undocumented.

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 (previous siblings of a content node), and the parenthetical 'lower menuindex in same parent' pins down what 'previous' means, which distinguishes it cleanly from evo.content.next_siblings. It stops short of naming that sibling explicitly, so it is strong but not maximally differentiated.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all. With siblings like evo.content.siblings, evo.content.siblings_range, evo.content.neighbors and evo.content.next_siblings available, the definition gives no conditions or exclusions for choosing among them; the agent must infer everything from the tool name.

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