Skip to main content
Glama
danielrosehill

Daniel Rosehill's MCP Installer

sync_registry

Update the local registry cache from GitHub to access the latest MCP server list for installation and configuration across multiple clients.

Instructions

Update the local registry cache from GitHub. Use this to get the latest MCP list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
forceNoForce refresh even if cache is fresh

Implementation Reference

  • The main handler for the 'sync_registry' tool call. It invokes syncRegistry() from registry.ts and formats the response as MCP content.
    case 'sync_registry': {
      const result = await syncRegistry();
      return {
        content: [{
          type: 'text',
          text: JSON.stringify({
            status: 'success',
            message: 'Registry synced from GitHub',
            ...result
          }, null, 2)
        }]
      };
    }
  • src/index.ts:131-144 (registration)
    Registers the 'sync_registry' tool in the tools array, including name, description, and input schema.
    {
      name: 'sync_registry',
      description: 'Update the local registry cache from GitHub. Use this to get the latest MCP list.',
      inputSchema: {
        type: 'object',
        properties: {
          force: {
            type: 'boolean',
            description: 'Force refresh even if cache is fresh',
            default: true
          }
        }
      }
    },
  • The core implementation of syncRegistry, which forces a registry refresh via getRegistry(true) and returns version, MCP count, and update time.
    export async function syncRegistry(): Promise<{ version: string; mcpCount: number; updated: string }> {
      const registry = await getRegistry(true);
      return {
        version: registry.version,
        mcpCount: registry.mcps.length,
        updated: registry.updated
      };
    }
  • Supporting function getRegistry used by syncRegistry to fetch or load cached registry data, with forceRefresh option to bypass cache.
    export async function getRegistry(forceRefresh = false): Promise<Registry> {
      // Check cache first (unless forcing refresh)
      if (!forceRefresh) {
        const cached = readCache();
        if (cached) {
          return cached;
        }
      }
    
      // Try to fetch from remote
      try {
        const registry = await fetchRemoteRegistry();
        writeCache(registry);
        return registry;
      } catch (error) {
        console.error('Failed to fetch remote registry:', error);
    
        // Fall back to cache (even if expired)
        try {
          if (fs.existsSync(CACHE_FILE)) {
            const data = fs.readFileSync(CACHE_FILE, 'utf-8');
            const cache: CacheEntry = JSON.parse(data);
            console.error('Using expired cache as fallback');
            return cache.registry;
          }
        } catch {
          // Ignore cache read errors
        }
    
        // Fall back to local registry
        const local = loadLocalRegistry();
        if (local) {
          console.error('Using local registry as fallback');
          return local;
        }
    
        throw new Error('No registry available (remote fetch failed and no local fallback)');
      }
    }
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the tool's purpose (updating cache from GitHub) but lacks details on behavioral traits like potential rate limits, network dependencies, authentication needs, or what happens if GitHub is unreachable. The description adds basic context but doesn't fully compensate for the absence of 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 description is two concise sentences with zero waste. The first sentence states the core action and resource, and the second provides clear usage context. It's front-loaded and appropriately sized for the tool's complexity.

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

Completeness3/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 (network operation to update cache), lack of annotations, and no output schema, the description is somewhat complete but has gaps. It explains the purpose and usage but doesn't cover behavioral aspects like error handling or response format. It's adequate as a minimum viable description but could be more comprehensive.

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 input schema has 100% description coverage, with the 'force' parameter well-documented in the schema. The description doesn't add any parameter-specific information beyond what the schema provides, but since there's only one optional parameter with full schema coverage, the baseline is high. No additional semantic value is needed here.

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 action ('Update the local registry cache') and resource ('from GitHub'), with explicit purpose ('to get the latest MCP list'). It distinguishes from siblings like 'list_mcps' (which likely shows cached data) by emphasizing the refresh/update function.

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

Usage Guidelines4/5

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

The description provides clear context for when to use this tool ('to get the latest MCP list'), implying it should be used when fresh data is needed. However, it doesn't explicitly state when NOT to use it or name specific alternatives among the sibling tools, such as contrasting with 'list_mcps' for cached vs. fresh data.

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/danielrosehill/My-MCP-Installer'

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