Skip to main content
Glama

get_all_details

Retrieve comprehensive lifecycle details for all versions of a software product to check end-of-life dates, support status, and upgrade recommendations.

Instructions

Get comprehensive lifecycle details for all versions of a product

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
productYesSoftware product name (e.g., python, nodejs)

Implementation Reference

  • Executes the get_all_details tool: fetches all cycles for the product from EOL API, validates each against current date, and returns detailed JSON with validation status.
    private async handleGetAllDetails(args: GetAllDetailsArgs) {
      const { product } = args;
    
      if (!this.availableProducts.includes(product)) {
        return {
          content: [{
            type: "text",
            text: `Invalid product: ${product}. Use list_products tool to see available products.`
          }],
          isError: true
        };
      }
    
      try {
        const cycles = await this.getProductDetails(product);
        const currentDate = new Date();
    
        // Add validation results for each cycle
        const detailedCycles = cycles.map(cycle => {
          const validation = this.validateVersion(cycle, currentDate);
          return {
            ...cycle,
            validation: {
              is_valid: validation.isValid,
              days_to_eol: validation.daysToEol,
              is_supported: validation.isSupported,
              message: validation.validationMessage
            }
          };
        });
    
        return {
          content: [{
            type: "text",
            text: JSON.stringify({
              product,
              current_date: currentDate.toISOString(),
              cycles: detailedCycles
            }, null, 2)
          }]
        };
      } catch (error) {
        if (axios.isAxiosError(error)) {
          return {
            content: [{
              type: "text",
              text: `API error: ${error.response?.data?.message ?? error.message}`
            }],
            isError: true
          };
        }
        throw error;
      }
    }
  • src/index.ts:363-377 (registration)
    Registers the get_all_details tool in the ListToolsRequestSchema handler, defining its name, description, and input schema.
    {
      name: "get_all_details",
      description: "Get comprehensive lifecycle details for all versions of a product",
      inputSchema: {
        type: "object",
        properties: {
          product: {
            type: "string",
            description: "Software product name (e.g., python, nodejs)",
            examples: ["python", "nodejs"]
          }
        },
        required: ["product"]
      }
    }
  • TypeScript interface defining the input arguments for the get_all_details tool.
    export interface GetAllDetailsArgs {
      product: string;
    }
  • Type guard function to validate input arguments match GetAllDetailsArgs interface.
    export function isValidGetAllDetailsArgs(args: any): args is GetAllDetailsArgs {
      return (
        typeof args === "object" &&
        args !== null &&
        "product" in args &&
        typeof args.product === "string"
      );
    }
  • src/index.ts:427-435 (registration)
    Dispatcher case in CallToolRequestSchema handler that validates args and invokes the get_all_details handler.
    case "get_all_details": {
      if (!isValidGetAllDetailsArgs(args)) {
        throw new McpError(
          ErrorCode.InvalidParams,
          "Invalid get all details arguments"
        );
      }
      return this.handleGetAllDetails(args);
    }
Behavior2/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 states the tool retrieves details but doesn't describe what 'comprehensive lifecycle details' includes (e.g., release dates, support status, vulnerabilities), whether it's a read-only operation, potential rate limits, or error handling. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 directly states the tool's purpose without unnecessary words. It is appropriately sized and front-loaded, with every part contributing to understanding. This earns a 5 for optimal conciseness and structure.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (retrieving lifecycle details for all versions) and lack of annotations and output schema, the description is incomplete. It doesn't explain what 'comprehensive lifecycle details' entails, how results are structured, or any behavioral traits. For a tool with no structured data beyond the input schema, this leaves too many unknowns for effective use.

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?

The input schema has 100% description coverage, clearly documenting the single 'product' parameter with examples. The description adds no additional parameter semantics beyond implying the tool operates on a product, which the schema already covers. According to the rules, with high schema coverage, the baseline is 3 even without param info in the description.

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 verb ('Get') and resource ('comprehensive lifecycle details for all versions of a product'), making the purpose specific and understandable. It distinguishes from siblings like 'check_version' (single version) or 'list_products' (product names only), but doesn't explicitly name alternatives. This earns a 4 for clarity without full sibling differentiation.

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 implies usage when comprehensive lifecycle details across all versions are needed, as opposed to checking a single version or listing products. However, it doesn't explicitly state when to use this tool versus alternatives like 'check_cve' or 'compare_versions', nor does it provide exclusions or prerequisites. This results in a 3 for implied but not explicit guidance.

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/ducthinh993/mcp-server-endoflife'

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