Skip to main content
Glama
Sign In
Sitecore Community MCP

Sitecore Community MCP

by gherisalim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

security-enable-user

Enable a Sitecore user account by providing its identity, restoring access for a disabled user in Sitecore XM, XP, or SitecoreAI.

Instructions

Enables the Sitecore user account.

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": {
      "identity": "<identity>"
    },
    "name": "security-enable-user"
  }
}

Input Schema

NameRequiredDescriptionDefault
identityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.3

TDQS

C2.6/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, and 'Enables' is consistent with that. Beyond the annotations, though, the description says nothing about what enabling actually does (login capability, effect on existing sessions/permissions) or what permissions are required. It adds no behavioral context of its own.

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 short sentence with no filler, and the action is front-loaded. However, its brevity comes from under-specification rather than disciplined editing, so it does not earn top marks.

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 state-changing account tool with no output schema and an undocumented parameter, the description is far too thin. It omits what the operation affects, required privileges, and the identity format, leaving the agent to guess before invoking it.

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?

The single required parameter 'identity' has 0% schema description coverage and the description never mentions it. It is unclear whether identity is a username, an email, or a domain-qualified account name, and the description does nothing to compensate.

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 gives a specific verb ('Enables') and resource ('the Sitecore user account'), so the agent knows exactly what state change occurs. It does not, however, differentiate this from close siblings like security-unlock-user or security-set-user, which also modify account state.

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 guidance on when to use this rather than security-disable-user (the inverse), security-unlock-user, or security-set-user, and no mention of prerequisites such as admin rights. Usage must be inferred entirely 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.

Deploy Server

Other Tools