Skip to main content
Glama
zb-ss

Servonaut

by zb-ss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

cloudwatch_list_log_groups

List AWS CloudWatch log groups by name prefix and see stored bytes and retention per group.

Instructions

List AWS CloudWatch log groups, optionally filtered by name prefix. Shows stored bytes and retention per group.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
prefixNoFilter to log groups whose name starts with this prefix.
regionNoAWS region (defaults to the boto3 default region when empty).
accountNoAWS account label to act in; omit for the default account.

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

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses that the tool is a listing operation and what it returns (stored bytes and retention per group), but does not state authentication requirements, explicit read-only status, or pagination limits. This is minimum viable for a read-only list tool.

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 concise sentences, front-loaded with the core action. No wasted words.

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 list tool with a fully documented schema and no output schema, the description provides the necessary purpose and return-value context. It omits usage guidance and behavioral details, but those are handled by other dimensions.

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 baseline is 3. The description's mention of the prefix filter restates what the schema already documents and adds no new parameter semantics.

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?

The description states a specific verb and resource ('List AWS CloudWatch log groups') plus an optional filter condition. It does not explicitly differentiate from sibling CloudWatch tools (e.g., cloudwatch_get_log_events), so it falls short of a 5.

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

Usage Guidelines2/5

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

No when-to-use guidance or alternative selection criteria. The only contextual detail is the optional prefix filter, which is parameter information rather than usage direction.

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