Skip to main content
Glama
zb-ss

Servonaut

by zb-ss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

aws_stop_instance

Stops a running AWS EC2 instance to pause instance-hours while preserving EBS disk state; restart later. Confirm first—the instance stays offline until started again.

Instructions

Stop a running AWS EC2 instance (EBS-backed; restartable). Disk state preserved; EBS billing continues, instance-hours pause. Confirm with the user — outage until the instance is started again.

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.4/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and delivers: EBS-backed/restartable semantics, that disk state is preserved, that EBS billing continues while instance-hours pause, and that user confirmation is required. These are exactly the side effects an agent must know before invoking a mutating call.

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?

Three compact sentences, front-loaded with the action, then consequences, then the confirmation requirement. No filler and every clause carries operational meaning.

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 mutation tool with no annotations and no output schema, the description covers the safety-critical behavior well. It stops short of stating required IAM permissions or how to confirm the resulting state, which would round it out.

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 instance_id, region, and account are already documented in the schema, including the '<account>/<id or name>' addressing form. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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?

States a specific verb (Stop) and resource (AWS EC2 instance) with a scope qualifier (EBS-backed; restartable). It is immediately distinguishable from the siblings aws_start_instance, aws_reboot_instance, and aws_terminate_instance because it explicitly frames the operation as reversible.

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?

The description gives clear operating context — this causes an outage until the instance is restarted, and the agent should confirm with the user first. The contrast with termination is implicit via 'restartable' and 'disk state preserved', but no alternative tool is named and no exclusion is stated outright.

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