Skip to main content
Glama
zb-ss

Servonaut

by zb-ss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

aws_reboot_instance

Restart a running AWS EC2 instance by ID and region. Confirm with the user before calling; billing continues during the brief OS-level reboot.

Instructions

Reboot a running AWS EC2 instance. Brief OS-level restart; billing continues. Confirm with the user before calling.

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/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 meaningful behavior: it is a 'brief OS-level restart' and 'billing continues,' which tells the agent the instance stays up and costs are unaffected, unlike stop/terminate. It omits disruption details (downtime, in-flight connection loss) and any permission requirements, keeping it short of 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?

Three compact clauses, front-loaded with the operation, followed by effect and safety instruction. Every clause earns its place with no filler.

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 simple single-instance mutation with no annotations and no output schema, the description covers what it does, its side effects, and the confirmation requirement. It would be complete at 5 if it mentioned that the instance must be in a running state (implied by 'running') or noted any permission/return expectations.

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 region, account, and instance_id (including the '<account>/<id or name>' form) are already fully documented in the schema. 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 (Reboot) and resource (a running AWS EC2 instance), which cleanly separates it from the sibling mutation tools aws_stop_instance, aws_start_instance, and aws_terminate_instance. An agent can identify the operation without opening the schema.

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

Usage Guidelines3/5

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

The description gives one actionable precondition, 'Confirm with the user before calling,' which is real usage guidance. However, it never says when to choose reboot over stop/start (e.g. to clear a hung process without losing the instance) or any exclusions, so the routing guidance is only implied.

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