Skip to main content
Glama

Update Status

localnest_update_status
Read-onlyIdempotent

Check for available updates to the LocalNest MCP server, verifying if a newer version exists in the npm registry. Supports stable and beta channels with configurable response formats.

Instructions

Check npm for the latest localnest-mcp version on the selected channel (cached, default every 120 minutes).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
force_checkNo
channelNostable
response_formatNojson

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
metaNo

Implementation Reference

  • Registration and handler mapping for localnest_update_status. It uses the `updates.getStatus` method.
    registerJsonTool(
      ['localnest_update_status'],
      {
        title: 'Update Status',
        description: 'Check npm for the latest localnest-mcp version on the selected channel (cached, default every 120 minutes).',
        inputSchema: {
          force_check: z.boolean().default(false),
          channel: z.enum(['stable', 'beta']).default('stable')
        },
        annotations: {
          readOnlyHint: true,
          destructiveHint: false,
          idempotentHint: true,
          openWorldHint: true
        }
      },
      async ({ force_check, channel }) => normalizeUpdateStatus(await updates.getStatus({ force: force_check, channel }))
    );
  • The implementation of the logic behind `localnest_update_status` which checks npm for new versions and manages the cache.
    async getStatus({ force = false, channel = 'stable' } = {}) {
      const now = Date.now();
      const cache = this.readCache();
      const normalizedChannel = normalizeUpdateChannel(channel) || 'stable';
    
      if (!this.shouldRefresh(cache, now, force) && cache && (cache.update_channel || 'stable') === normalizedChannel) {
        return this.withStatusMetadata({
          ...cache,
          stale: false,
          source: 'cache'
        }, now);
      }
    
      try {
        const latestVersion = this.checkLatestFromNpm(normalizedChannel);
        const isOutdated = compareVersions(latestVersion, this.currentVersion) > 0;
        const refreshed = {
          package_name: this.packageName,
          current_version: this.currentVersion,
          latest_version: latestVersion,
          update_channel: normalizedChannel,
          is_outdated: isOutdated,
          checked_via: 'npm view',
          source: 'live',
          last_checked_at: new Date(now).toISOString(),
          last_check_ok: true,
          error: null,
          recommend_update_prompt: isOutdated,
          next_check_after_minutes: this.checkIntervalMinutes,
          cache_path: this.cachePath
        };
        this.writeCache(refreshed);
        return this.withStatusMetadata(refreshed, now);
      } catch (error) {
        const fallbackLatest = cache?.latest_version || this.currentVersion;
        const fallbackChannel = cache?.update_channel || normalizedChannel;
        const isOutdated = compareVersions(fallbackLatest, this.currentVersion) > 0;
        const failed = {
          package_name: this.packageName,
          current_version: this.currentVersion,
          latest_version: fallbackLatest,
          update_channel: fallbackChannel,
          is_outdated: isOutdated,
          checked_via: 'npm view',
          source: cache ? 'cache-fallback' : 'error',
          last_checked_at: new Date(now).toISOString(),
          last_check_ok: false,
          error: String(error?.message || error),
          recommend_update_prompt: isOutdated,
          next_check_after_minutes: this.failureBackoffMinutes,
          cache_path: this.cachePath
        };
        this.writeCache(failed);
        return this.withStatusMetadata(failed, now);
      }
    }
Behavior4/5

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

While annotations declare readOnly, idempotent, and non-destructive traits, the description adds valuable behavioral context: the 120-minute cache duration, the npm registry as the external data source (aligning with openWorldHint), and the implication that force_check bypasses caching. No contradiction with annotations.

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 single 15-word sentence is exceptionally dense and efficient, packing the action (Check), resource (npm version), scope (selected channel), and behavioral trait (cached/120 minutes) without waste. Every clause earns its place.

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?

Given the tool's moderate complexity (3 simple parameters, 2 enums) and the presence of an output schema, the description provides adequate context when combined with annotations. The caching detail is particularly valuable. Only the omission of response_format semantics prevents a 5.

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?

With 0% schema description coverage, the description must compensate for three undocumented parameters. It successfully maps 'selected channel' to the channel parameter and implies force_check through the caching discussion, but completely omits response_format. This partial compensation warrants a middle score.

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 clearly states the tool 'Check[s] npm for the latest localnest-mcp version on the selected channel', specifying the action, data source, and scope. It successfully clarifies that this is a read operation (checking for updates) despite the potentially misleading 'update' in the tool name, distinguishing it from actual update operations.

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

Usage Guidelines3/5

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

The description provides implicit usage guidance by noting the caching behavior ('cached, default every 120 minutes'), which signals when to use force_check. However, it lacks explicit when-to-use guidance or differentiation from siblings like localnest_server_status or localnest_update_self.

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/wmt-mobile/localnest'

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