Skip to main content
Glama
zb-ss

Servonaut

by zb-ss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

aws_list_amis

List AWS AMIs in a region, sorted by creation date descending, to find available machine images. Filter by name glob, select owners (default: amazon), and limit results to 50.

Instructions

List AMIs in the given region, sorted newest-first. Filter by partial name match (case-sensitive glob). Defaults to AMIs owned by 'amazon'. max_results capped at 50 to bound describe API consumption.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownersNoOwner account IDs or aliases (default: ['amazon']).
regionYesAWS region (e.g. us-east-1).
accountNoAWS account label to act in; omit for the default account.
max_resultsNoMaximum number of results (default: 50).
name_filterNoPartial name glob filter (case-sensitive). Default: ''.

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

A3.8/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 well: it discloses sort order (newest-first), filter semantics (case-sensitive glob), the default owner scope, and the rationale for the 50-result cap (bounding describe API consumption). It stops short of stating read-only nature explicitly or any error/auth behavior, but the behavioral context is substantial.

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 sentences, each earning its place, with the core action front-loaded and the constraints following. No filler or redundancy.

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?

Covers purpose, filtering, defaults, and result bounding, which is enough to call the tool correctly. Without an output schema it doesn't describe the returned AMI fields, but for a straightforward list tool the description is nearly complete.

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 all five parameters. The description reinforces defaults (amazon, case-sensitive glob, 50 cap) but adds little beyond what the schema provides, making the baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

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

States a specific verb and resource ('List AMIs in the given region') with scope (region-bound) and ordering (newest-first). The resource is unique among the aws_list_* siblings, so an agent can disambiguate it, though it doesn't explicitly name any alternative tool.

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?

Provides default behavior (amazon-owned) and filter semantics but gives no explicit when-to-use guidance or exclusions relative to siblings like aws_list_instance_types or aws_call. Usage is implied rather than stated.

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