Skip to main content
Glama

get_version

Retrieve Tailscale version details using the standardized Model Context Protocol interface to support automated network management and monitoring tasks.

Instructions

Get Tailscale version information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get_version' tool. It invokes the unified Tailscale client's getVersion method and formats the result as a success response.
    async function getVersion(
      _args: Record<string, unknown>,
      context: ToolContext,
    ): Promise<CallToolResult> {
      try {
        logger.debug("Getting Tailscale version");
    
        // Use unified client - this operation is CLI-only
        const result = await context.client.getVersion();
    
        if (!result.success) {
          return returnToolError(result.error);
        }
    
        return returnToolSuccess(
          `Tailscale version information:\n\n${result.data}`,
        );
      } catch (error: unknown) {
        logger.error("Error getting version:", error);
        return returnToolError(error);
      }
    }
  • The registration of the 'get_version' tool within the networkTools module, including empty input schema and reference to the handler.
    {
      name: "get_version",
      description: "Get Tailscale version information",
      inputSchema: z.object({}),
      handler: getVersion,
    },
  • Supporting method in UnifiedTailscaleClient that delegates to either Tailscale API or CLI to retrieve version information, used by the tool handler.
    async getVersion(): Promise<
      UnifiedResponse<string | { version: string; apiVersion: string }>
    > {
      if (this.shouldUseAPI("getVersion")) {
        const response = await this.api.getVersion();
        return this.normalizeAPIResponse(response);
      }
      if (!this.cliAvailable) {
        return {
          success: false,
          error: "Version information is not available",
          source: "cli",
        };
      }
      const response = await this.cli.version();
      return this.normalizeCLIResponse(response);
    }
  • Tailscale API client method for fetching version information via HTTP GET to /api/v2/version, called by unified client if API preferred.
    async getDevice(
      deviceId: string,
    ): Promise<TailscaleAPIResponse<TailscaleDevice>> {
      try {
        const response = await this.client.get(`/device/${deviceId}`);
        const device = TailscaleDeviceSchema.parse(response.data);
    
        return this.handleResponse({ ...response, data: device });
      } catch (error) {
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 what the tool does but doesn't reveal any behavioral traits such as whether it's read-only, requires authentication, has rate limits, or what the output format might be. For a tool with zero annotation coverage, this is inadequate.

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 with zero waste. It's front-loaded with the core purpose and uses clear language. Every word earns its place, making it easy to parse and understand quickly.

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 simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate. It states the purpose but lacks context about when to use it, behavioral traits, or output details. For a basic read operation, it's passable but could be more helpful with additional guidance.

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, and schema description coverage is 100%, so there's no need for parameter documentation in the description. The description correctly doesn't mention any parameters, which is appropriate. A baseline of 4 is given since no parameters exist, and the description doesn't introduce confusion.

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 resource ('Tailscale version information'), making it immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_network_status' or 'get_tailnet_info', which might also retrieve system information. The description is accurate but lacks sibling distinction.

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 context, prerequisites, or exclusions, leaving the agent to infer usage based on the tool name alone. This is a significant gap for a server with multiple 'get' tools that could overlap in functionality.

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

Related 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/HexSleeves/tailscale-mcp'

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