Skip to main content
Glama
zb-ss

Servonaut

by zb-ss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

aws_start_instance

Start a stopped AWS EC2 instance using its instance ID and region. Resumes billing; confirm with the user before calling.

Instructions

Start a stopped AWS EC2 instance. Requires both the instance ID and the region. Confirm with the user before calling — resumes billing while the instance is running.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regionYesAWS region (e.g. us-east-1).
accountNoAccount label the server is in; omit to use the account whose inventory lists it (else the default account).
instance_idYesEC2 instance ID (i-...); '<account>/<id or name>' picks the server of one AWS account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.28.0
    • addedInput schema / properties / account
      Added value: +{
+  "description": "Account label the server is in; omit to use the account whose inventory lists it (else the default account).",
+  "type": "string"
+}
    • changedInput schema / properties / instance_id / description
      Previous value: -"EC2 instance ID (i-...)."New value: +"EC2 instance ID (i-...); '<account>/<id or name>' picks the server of one AWS account."
  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 full burden and does disclose a real side effect most would miss: 'resumes billing while the instance is running.' The user-confirmation requirement is also a meaningful behavioral constraint. It omits auth/permission requirements and any error or state-transition behavior, so it falls short of 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?

Two sentences, zero waste, and well front-loaded: action first, then requirements, then the cautionary note. Every sentence earns its place.

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 an annotation-free mutation tool with no output schema, the description surfaces the two things an agent most needs — required inputs and the billing consequence plus confirmation gate. It does not address return behavior or failure modes, a minor gap given there is no output schema to lean on.

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 documents instance_id, region, and the optional account label in full detail. The description adds nothing about parameter formats or the account-qualified '<account>/<id>' syntax. Baseline 3 applies 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?

Precise verb+resource: 'Start a stopped AWS EC2 instance.' It is immediately distinguishable from the sibling mutators aws_stop_instance, aws_reboot_instance, and aws_terminate_instance without opening any schema.

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?

Gives a clear calling context ('Start a stopped instance') plus an explicit prerequisite ('Requires both the instance ID and the region') and a procedural gate ('Confirm with the user before calling'). It does not name alternatives (e.g. aws_stop_instance) or state when-not-to-use, so it stops short of the top tier.

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