Skip to main content
Glama
JaxonDigital

Optimizely DXP MCP Server

by JaxonDigital

get_version

Check the current version of the Optimizely DXP MCP Server and verify if updates are available from the NPM registry.

Instructions

📌 Get current MCP server version and update availability. REAL-TIME: <1s. Checks local version against NPM registry for updates. Use this to verify you have latest features and bug fixes. Returns current version, latest available version, and update available flag. Suggests npm update command if outdated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registration of the 'get_version' tool in the tool availability matrix, available for all hosting types with description 'Get MCP server version information'
    'get_version': {
        hostingTypes: ['dxp-paas', 'dxp-saas', 'self-hosted', 'unknown'],
        category: 'Support',
        description: 'Get MCP server version information'
    },
  • Handler function getVersion() that reads and returns the MCP server version from package.json or 'unknown' if failed
    getVersion() {
        try {
            const pkg = require('../package.json');
            return pkg.version;
        } catch (error) {
            return 'unknown';
        }
    }
  • Version checker that gets current version from package.json and checks for updates, likely related to version tool logic
    static async checkForUpdates(): Promise<UpdateInfo | null> {
        try {
            const currentVersion: string = packageJson.version;
            const packageName: string = packageJson.name;
    
            // Check npm registry for latest version
            const latestVersion = await this.getLatestVersion(packageName);
    
            if (latestVersion && this.isNewerVersion(currentVersion, latestVersion)) {
                return {
                    updateAvailable: true,
                    currentVersion,
                    latestVersion,
                    updateCommand: `npm install -g ${packageName}@latest`
                };
            }
    
            return {
                updateAvailable: false,
                currentVersion
            };
        } catch (error) {
            // Silently fail - don't interrupt the user's workflow
            console.error('Version check failed:', (error as Error).message);
            return null;
        }
    }
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes performance characteristics ('REAL-TIME: <1s'), external dependencies ('Checks local version against NPM registry'), and the action triggered by results ('Suggests npm update command if outdated'). However, it doesn't mention error handling or authentication requirements.

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 efficiently structured with an emoji visual cue, performance metric upfront, clear purpose statement, usage guidance, and output details - all in 4 concise sentences with zero redundant information. Every sentence adds essential value.

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 zero-parameter tool with no annotations or output schema, the description provides excellent context about what the tool does, when to use it, performance characteristics, and what information it returns. The only minor gap is lack of explicit error handling information, but overall it's quite complete for this simple tool.

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?

The tool has 0 parameters with 100% schema description coverage, so the baseline would be 3. The description adds value by explaining that no parameters are needed because it automatically checks both local and registry versions, providing context beyond the empty schema.

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 clearly states the specific verb ('Get') and resource ('current MCP server version and update availability'), distinguishing it from sibling tools like 'health_check' or 'status' by focusing on version information rather than operational status. It explicitly mentions checking against NPM registry, which further clarifies its unique purpose.

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?

The description explicitly states when to use this tool ('to verify you have latest features and bug fixes') and provides a clear alternative action ('Suggests npm update command if outdated'), giving the agent direct guidance on usage context and next steps based on the output.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/JaxonDigital/optimizely-dxp-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server