MCP SysOperator

aws_lambda

Manage AWS Lambda functions by listing, creating, updating, deleting, or invoking them through the MCP SysOperator server for cloud infrastructure automation.

Instructions

Manage AWS Lambda functions

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>",
      "region": "<region>"
    },
    "name": "aws_lambda"
  }
}

Input Schema

Name	Required	Description	Default
`action`	Yes
`region`	Yes
`name`	No
`zipFile`	No
`s3Bucket`	No
`s3Key`	No
`functionCode`	No
`runtime`	No
`handler`	No
`role`	No
`description`	No
`timeout`	No
`memorySize`	No
`environment`	No
`tags`	No
`payload`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedJan 30, 2026

TDQS

C2.2/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but offers minimal information. 'Manage' implies mutation capabilities, but it doesn't specify authentication requirements, rate limits, error handling, or side effects. The description fails to disclose critical behavioral traits like whether operations are idempotent, what permissions are needed, or how errors are returned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise at just three words, which is appropriate for its length. However, this conciseness comes at the cost of being under-specified for such a complex tool with 16 parameters. While front-loaded, it lacks the necessary detail that would justify its brevity for a multi-action management tool.

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

Completeness1/5

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

For a complex tool with 16 parameters, 0% schema description coverage, no annotations, no output schema, and multiple possible actions, the description is completely inadequate. It provides no information about return values, error conditions, authentication requirements, or how different actions behave. The agent would struggle to use this tool correctly without extensive trial and error.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, meaning none of the 16 parameters have descriptions in the schema. The tool description provides no parameter information whatsoever - it doesn't mention the 'action' parameter with its enum values, required 'region', or any of the other 14 parameters. This leaves the agent completely dependent on parameter names alone to guess functionality.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Manage AWS Lambda functions' states a general purpose but is vague about what management entails. It distinguishes from sibling tools by specifying AWS Lambda, but doesn't clarify the specific actions available (list, create, update, delete, invoke) which are only visible in the schema. The description lacks the specificity needed for an agent to understand the tool's exact capabilities.

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, appropriate contexts, or compare it to sibling AWS tools like aws_cloudformation or terraform. An agent must infer usage solely from the tool name and parameter schema without any contextual direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server