eMCP for Evolution CMS

Official

Overview Schema Source Related Servers Discussions Admin

Content Siblings Range Tool

evo.content.siblings_range

Read-only

Retrieves sibling nodes by menuindex position range within a parent set, enabling ordered content retrieval around a specific node.

Instructions

Read sibling nodes by menuindex position range for a node parent set.

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>",
      "from": "<from>",
      "limit": "<limit>"
    },
    "name": "evo.content.siblings_range"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

C2.8/5.0

Behavior3/5

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

readOnlyHint=true already covers safety, and the description adds that results are ordered by menuindex and bounded by a position range. It omits behavior an agent would want: whether the anchor node itself is included, what happens when the node has no parent or the range exceeds available siblings, and how results are ordered or paginated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with no filler, which is good, but it is terse to the point of under-specification rather than efficient. The core concept is front-loaded but expressed in compressed, ambiguous phrasing.

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?

A five-parameter read tool with no output schema, no parameter documentation, and only a readOnlyHint needs far more from its description. An agent can guess the intent but cannot reliably construct correct arguments or predict the response shape from this one sentence.

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% across five parameters, so the description must carry the load and largely does not. "Menuindex position range" maps loosely to from/to and "node parent set" hints at id, but inclusivity of bounds, null handling for to/offset, and the roles of limit and offset are all unexplained.

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 ("sibling nodes") with a scoping qualifier ("by menuindex position range for a node parent set"). It implicitly distinguishes itself from the plain sibling tools by naming a range, though the awkward phrase "node parent set" muddies whether it means the parent's children or the node's siblings.

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?

No when-to-use or when-not guidance appears. With siblings like evo.content.siblings, evo.content.children_range, evo.content.next_siblings and evo.content.prev_siblings, the description gives the agent no basis for choosing this tool over those alternatives.

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