lambda_restart_instancesRestart one or more running instances by id (a reboot — the instances are NOT destroyed and billing continues). Lambda Cloud REST: POST /api/v1/instance-operations/restart.
| Name | Required | Description | Default |
|---|---|---|---|
| instance_ids | Yes | Ids of the instances to restart. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description explicitly says 'instances are NOT destroyed', which directly contradicts the destructiveHint=true annotation. This is a critical inconsistency that misleads the agent about the tool's safety profile.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, action-oriented, with no redundant phrasing. The inclusion of the API endpoint adds useful context without bloat.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite the tool's simplicity, the annotation contradiction creates significant confusion about whether the operation is destructive. The description does not address this conflict or disclose potential service disruption, making the overall guidance inadequate.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema fully documents the only parameter (instance_ids) with a clear description. The description adds minimal extra meaning beyond the schema, so the baseline of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb 'Restart' with a clear resource ('one or more running instances by id') and clarifies it is a reboot, not destruction. This clearly distinguishes it from sibling tools like terminate_instances.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly states it applies to 'running instances' and explains that billing continues and instances are not destroyed, which helps an agent decide when a reboot is appropriate versus termination. However, no explicit alternative tool is named.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource and action (e.g., list_instances vs. launch_instance vs. terminate_instances). There is no overlap or ambiguity between tools; even similar resources like firewall_rules and firewall_rulesets are clearly differentiated by name and description.
All tool names follow the verb_noun pattern with the lambda_ prefix, using lowercase and underscores consistently. The verb clearly indicates the operation (list, get, create, delete, launch, update, restart, terminate), and the noun indicates the resource. Minor pluralization differences (e.g., list_instances vs. get_instance) are conventional and do not break consistency.
15 tools is well-scoped for a GPU cloud management server, covering instances, filesystems, firewall rules, images, instance types, and audit events. Each tool serves a distinct purpose and no unnecessary duplication exists.
The instance lifecycle is well covered with launch, get, list, update, restart, and terminate. Filesystem and firewall read operations are present, but firewall rule/ruleset management (create/update/delete) is missing, which is a minor gap that may require working around via the dashboard.