Skip to main content
Glama
danielrosehill

Daniel Rosehill's MCP Installer

get_info

Retrieve installer details, registry URL, cache location, and supported clients for MCP server configuration management.

Instructions

Get information about the installer, registry URL, cache location, and supported clients.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler implementation for the 'get_info' tool. It fetches registry info, client info, supported clients, and the registry data, then returns a formatted JSON response with details about the installer.
    case 'get_info': {
      const registryInfo = getRegistryInfo();
      const clientInfo = getAllClientInfo();
      let registry;
      try {
        registry = await getRegistry();
      } catch {
        registry = null;
      }
    
      return {
        content: [{
          type: 'text',
          text: JSON.stringify({
            name: 'daniel-rosehill-mcps',
            version: '1.0.0',
            description: "Daniel Rosehill's personal MCP installer",
            registry: {
              url: registryInfo.registryUrl,
              cache_dir: registryInfo.cacheDir,
              version: registry?.version || 'unavailable',
              mcp_count: registry?.mcps.length || 0,
              last_updated: registry?.updated || 'unavailable'
            },
            supported_clients: getSupportedClients(),
            clients: clientInfo
          }, null, 2)
        }]
      };
    }
  • Schema definition for the 'get_info' tool, specifying its name, description, and empty input schema.
    {
      name: 'get_info',
      description: 'Get information about the installer, registry URL, cache location, and supported clients.',
      inputSchema: {
        type: 'object',
        properties: {}
      }
    }
  • src/index.ts:176-178 (registration)
    Registers the list of available tools, including 'get_info', for the ListToolsRequestSchema.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools
    }));
Behavior2/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 of behavioral disclosure. It states this is a read operation ('Get information'), implying it's non-destructive, but doesn't clarify aspects like authentication needs, rate limits, or response format. For a tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves beyond basic purpose.

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 a single, efficient sentence that front-loads the purpose ('Get information') and lists specific details without unnecessary words. Every element (installer, registry URL, cache location, supported clients) earns its place by clarifying scope, making it appropriately sized and structured for quick comprehension.

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 low complexity (no parameters, no output schema, no annotations), the description is adequate but not fully complete. It covers the purpose and scope well, but without annotations or output schema, it should ideally mention behavioral traits (e.g., that it's a safe read operation) or response format to better guide usage. It meets minimum viability but has clear gaps in context.

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 zero parameters, and schema description coverage is 100%, so there's no need for parameter details in the description. The baseline for zero parameters is 4, as the description appropriately omits parameter information. It doesn't add semantics beyond the schema, but that's acceptable given the lack of parameters.

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's purpose with a specific verb ('Get') and enumerates the types of information retrieved (installer, registry URL, cache location, supported clients). It distinguishes itself from siblings like 'list_installed' or 'list_mcps' by focusing on system configuration rather than installed packages. However, it doesn't explicitly contrast with all siblings, preventing a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing the installer running), exclusions (e.g., not for modifying settings), or comparisons to siblings like 'list_mcps' (which might list available packages). Without such context, users must infer usage from the purpose alone.

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