Skip to main content
Glama

list_lambda_functions

Lists AWS Lambda functions with their runtimes and last modified dates to monitor and manage serverless resources.

Instructions

Lists Lambda functions with runtimes and last modified dates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'list_lambda_functions' tool. It uses the LambdaClient to send a ListFunctionsCommand, maps the response to include FunctionName, Runtime, LastModified, Handler, and CodeSize, and returns the JSON stringified list.
    if (name === "list_lambda_functions") {
        const command = new ListFunctionsCommand({});
        const response = await lambdaClient.send(command);
    
        const funcs = response.Functions?.map(f => ({
            FunctionName: f.FunctionName,
            Runtime: f.Runtime,
            LastModified: f.LastModified,
            Handler: f.Handler,
            CodeSize: f.CodeSize
        })) || [];
    
        return {
            content: [{ type: "text", text: JSON.stringify(funcs, null, 2) }]
        };
    }
  • src/index.ts:393-399 (registration)
    Registration of the 'list_lambda_functions' tool in the ListTools response, including its name, description, and empty input schema (no parameters required).
        name: "list_lambda_functions",
        description: "Lists Lambda functions with runtimes and last modified dates.",
        inputSchema: {
            type: "object",
            properties: {}
        }
    },
  • Input schema for the tool, which is an empty object (no input parameters needed).
        inputSchema: {
            type: "object",
            properties: {}
        }
    },
  • Initialization of the shared LambdaClient used by the handler.
    const lambdaClient = new LambdaClient({});
  • Import of LambdaClient and ListFunctionsCommand from AWS SDK.
    import { LambdaClient, ListFunctionsCommand } from "@aws-sdk/client-lambda";
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It mentions what data is returned (runtimes and last modified dates) but doesn't disclose behavioral traits like pagination, rate limits, authentication requirements, error handling, or whether it lists all functions or applies any filters. For a read operation with zero annotation coverage, this is insufficient.

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 action and includes relevant details. There's no wasted verbiage or redundancy, making it easy to parse 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 has no parameters, no annotations, and no output schema, the description provides basic purpose but lacks completeness. It doesn't cover behavioral aspects, output format details, or usage context, which are important for an agent to use it effectively in a server with many sibling tools.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, focusing instead on the output content. This meets the baseline for tools with no 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 verb ('Lists') and resource ('Lambda functions'), specifying what information is included ('with runtimes and last modified dates'). It distinguishes from generic list tools by specifying the AWS Lambda context, though it doesn't explicitly differentiate from potential similar list tools in the sibling set.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, context, or any sibling tools that might be relevant for related queries. It's a standalone statement with no usage context.

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