Skip to main content
Glama

list_products

Browse or search software products to check end-of-life dates, support status, and security information using real-time data from the endoflife.date API.

Instructions

Browse or search available software products

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filterNoOptional search term to filter products

Implementation Reference

  • The main handler function for the list_products tool. It filters the list of available products based on an optional filter argument and returns the JSON stringified list.
    private async handleListProducts(args: { filter?: string }) {
      const { filter } = args;
      let products = this.availableProducts;
    
      if (filter) {
        products = products.filter(p =>
          p.toLowerCase().includes(filter.toLowerCase())
        );
      }
    
      return {
        content: [{
          type: "text",
          text: JSON.stringify(products, null, 2)
        }]
      };
    }
  • TypeScript interface defining the input arguments for the list_products tool.
    export interface ListProductsArgs {
      filter?: string;
    }
  • Type guard function for validating list_products input arguments.
    export function isValidListProductsArgs(args: any): args is ListProductsArgs {
      return (
        typeof args === "object" &&
        args !== null &&
        (args.filter === undefined || typeof args.filter === "string")
      );
    }
  • src/index.ts:329-342 (registration)
    Tool registration in the listTools handler, defining name, description, and input schema.
    {
      name: "list_products",
      description: "Browse or search available software products",
      inputSchema: {
        type: "object",
        properties: {
          filter: {
            type: "string",
            description: "Optional search term to filter products",
            examples: ["python", "linux", "database"]
          }
        }
      }
    },
  • src/index.ts:407-414 (registration)
    Dispatch logic in the callTool handler that validates arguments and invokes the list_products handler.
    case "list_products":
      if (!isValidListProductsArgs(args)) {
        throw new McpError(
          ErrorCode.InvalidParams,
          "Invalid list products arguments"
        );
      }
      return this.handleListProducts(args);
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. While 'browse or search' implies a read-only operation, it doesn't specify whether this tool requires authentication, has rate limits, returns paginated results, or what the output format looks like (especially since there's no output schema). For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 function without unnecessary words. It's front-loaded with the core purpose ('Browse or search available software products'), making it easy for an agent to parse quickly. Every word earns its place.

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 lack of annotations and output schema, the description is incomplete for effective tool use. It doesn't explain what 'browse' entails (e.g., listing all products vs. paginated results), how search filtering works beyond the schema, or what the return values include (e.g., product names, IDs, versions). For a tool with no structured output documentation, the description should provide more context about expected behavior and results.

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 description mentions 'search' which aligns with the 'filter' parameter in the schema, but adds no additional semantic context beyond what the schema already provides (e.g., the schema's description covers 'Optional search term to filter products' with examples). With 100% schema description coverage and only one parameter, the baseline score of 3 is appropriate as the schema does the heavy lifting.

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 'Browse or search available software products' clearly states the verb ('browse or search') and resource ('software products'), making the purpose understandable. However, it doesn't explicitly differentiate this tool from its siblings like 'check_cve' or 'compare_versions', which appear to be more specific analysis tools rather than general browsing/searching.

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, appropriate contexts, or comparisons to sibling tools like 'get_all_details' (which might return comprehensive product information). Without such guidance, the agent must infer usage from the tool name and schema 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/ducthinh993/mcp-server-endoflife'

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