Skip to main content
Glama

list_expiring_certificates

Identify AWS ACM certificates approaching expiration within a specified timeframe to facilitate timely renewal and prevent service disruptions.

Instructions

Lists ACM certificates expiring within the specified days.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoNumber of days threshold (default: 30).

Implementation Reference

  • Handler function that executes the tool logic: lists ACM certificates using ListCertificatesCommand, describes each to check expiration date with DescribeCertificateCommand, filters those expiring within 'days' threshold (default 30), and returns a JSON list.
    if (name === "list_expiring_certificates") {
        const days = (args as any)?.days || 30;
        const thresholdDate = new Date(Date.now() + days * 24 * 60 * 60 * 1000);
    
        const listCmd = new ListCertificatesCommand({});
        const listResp = await acmClient.send(listCmd); // Note: paginates 1000 by default
    
        const expiringCerts = [];
    
        // We need to describe to get 'NotAfter'
        for (const certSummary of listResp.CertificateSummaryList || []) {
            if (!certSummary.CertificateArn) continue;
            try {
                const descCmd = new DescribeCertificateCommand({ CertificateArn: certSummary.CertificateArn });
                const descResp = await acmClient.send(descCmd);
                const cert = descResp.Certificate;
    
                if (cert && cert.NotAfter && cert.NotAfter < thresholdDate) {
                    expiringCerts.push({
                        DomainName: cert.DomainName,
                        CertificateArn: cert.CertificateArn,
                        NotAfter: cert.NotAfter,
                        Status: cert.Status,
                        InUseBy: cert.InUseBy
                    });
                }
            } catch (err) {
                // Ignore
            }
        }
    
        return {
            content: [{ type: "text", text: JSON.stringify(expiringCerts, null, 2) }]
        };
    }
  • src/index.ts:372-383 (registration)
    Tool registration in the ListToolsRequestSchema handler, including name, description, and input schema.
        name: "list_expiring_certificates",
        description: "Lists ACM certificates expiring within the specified days.",
        inputSchema: {
            type: "object",
            properties: {
                days: {
                    type: "number",
                    description: "Number of days threshold (default: 30)."
                }
            }
        }
    },
  • Input schema for the tool parameters.
    inputSchema: {
        type: "object",
        properties: {
            days: {
                type: "number",
                description: "Number of days threshold (default: 30)."
            }
        }
    }
  • ACMClient initialization used by the handler.
    const acmClient = new ACMClient({});
  • Import of ACMClient, ListCertificatesCommand, and DescribeCertificateCommand.
    import { ACMClient, ListCertificatesCommand, DescribeCertificateCommand } from "@aws-sdk/client-acm";
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. It mentions listing certificates but doesn't disclose behavioral traits like pagination, rate limits, authentication requirements, or what 'lists' entails (e.g., format, completeness). For a read operation with zero annotation coverage, this leaves significant gaps in understanding how the tool behaves.

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 core functionality without unnecessary words. It's appropriately sized for a simple tool with one parameter, earning full marks for conciseness.

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 (one optional parameter, no output schema, no annotations), the description is minimally adequate. However, it lacks details on output format (e.g., what data is returned) and behavioral context, which would be helpful for an agent to use it effectively. It meets basic needs but has clear gaps.

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, with the 'days' parameter documented as 'Number of days threshold (default: 30).' The description adds minimal value by mentioning 'specified days,' which aligns with the schema but doesn't provide additional semantics like examples or edge cases. Baseline 3 is appropriate when 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 clearly states the verb ('Lists') and resource ('ACM certificates expiring within the specified days'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'list_certificates' (which doesn't exist in the provided list), so it misses the highest 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 (e.g., other AWS certificate-related tools not listed here) or any prerequisites. It simply states what it does without context about appropriate scenarios or exclusions.

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/bhaveshopss/MCP-server'

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