Skip to main content
Glama
zb-ss

Servonaut

by zb-ss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

aws_run_instances

Launch one or more AWS EC2 instances by specifying region, AMI, type, subnet, security groups, and key pair, then confirm before billing starts.

Instructions

Launch one or more new AWS EC2 instances. Costs money — billing starts immediately. Reserved for dangerous guard mode. Summarise AMI, instance type, region, count, and confirm with the user before calling. Returns JSON with the new instance IDs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoNumber of instances to launch (1–10, default 1).
ami_idYesAMI ID (ami-...).
regionYesAWS region (e.g. us-east-1).
accountNoAWS account label to act in; omit for the default account.
key_nameYesEC2 key-pair name (1–255 chars).
name_tagYesName tag for the launched instance(s) (1–255 printable chars).
subnet_idYesVPC subnet ID (subnet-...).
instance_typeYesEC2 instance type (e.g. t3.micro).
security_group_idsYesOne or more security group IDs (sg-...).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.28.0
    • addedInput schema / properties / account
      Added value: +{
+  "description": "AWS account label to act in; omit for the default account.",
+  "type": "string"
+}
  2. Addedv2.24.0
  3. Removedv2.23.8
  4. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the behavioural burden and discloses critical traits: immediate billing, cost, dangerous guard mode, required user confirmation, and that it returns JSON with new instance IDs. It omits permissions requirements, failure modes, and resource persistence implications, keeping it below a 5.

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 front-loaded and tightly structured: purpose first, then the cost warning, guard-mode restriction, confirmation procedure, and return format. Every sentence adds distinct decision-relevant information with no waste.

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

Completeness4/5

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

For a complex, dangerous mutation tool with nine parameters and no annotations or output schema, the description covers the key decision points: cost, guard mode, confirmation, and return shape. It is missing details about IAM permissions and partial-failure behaviour, but is otherwise sufficient.

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?

Schema description coverage is 100%, so the schema already defines all nine parameters. The description names a subset (AMI, instance type, region, count) but adds no syntax or meaning beyond what the schema provides, matching the baseline of 3 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.

Purpose5/5

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

The description states a specific verb and resource: 'Launch one or more new AWS EC2 instances.' The word 'new' distinguishes it from sibling aws_start_instance, which starts existing stopped instances, so an agent can tell them apart without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear usage context: 'Reserved for dangerous guard mode' and requires summarising parameters and confirming with the user before calling. It does not explicitly name alternatives such as aws_start_instance for existing instances, so it falls short of full when/when-not guidance.

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

Deploy Server

Other Tools