infrawise

Overview Schema Source Related Servers Discussions Admin

CloudWatch log group metadata

get_log_errors

Read-only

Lists CloudWatch log group names and retention metadata to check retention policies; it does not read log events or diagnose runtime errors.

Instructions

Returns CloudWatch log group names and retention metadata without reading log events. The legacy get_log_errors name is retained for compatibility; errorCount is null, topErrorPatterns is empty, and errorsObserved is false because no message bodies are requested. Use logGroup to filter names. Call when checking retention policies; do NOT use to diagnose runtime errors or infer that no errors occurred.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_log_errors"
  }
}

Input Schema

Name	Required	Description	Default
`logGroup`	No	Filter to a specific log group name (optional)
`maxAgeSeconds`	No	Freshness tolerance in seconds. Advisory: the answer is returned either way, with dataHealth.withinRequestedAge reporting whether it met the tolerance. Nothing re-reads AWS on a tool call — run `infrawise analyze` to refresh. Pass a small value for point-in-time questions ("does this queue have a DLQ right now"); omit it for architecture questions where a day-old snapshot is fine.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.26.1Aug 14, 2026

addedInput schema / properties / maxAgeSeconds

Added value: +{
+  "description": "Freshness tolerance in seconds. Advisory: the answer is returned either way, with dataHealth.withinRequestedAge reporting whether it met the tolerance. Nothing re-reads AWS on a tool call — run `infrawise analyze` to refresh. Pass a small value for point-in-time questions (\"does this queue have a DLQ right now\"); omit it for architecture questions where a day-old snapshot is fine.",
+  "type": "number"
+}

First observedv0.1.0May 27, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing the exact response semantics: errorCount is null, topErrorPatterns is empty, errorsObserved is false, and no message bodies are fetched. Since there is no output schema, this is the only place an agent learns how to interpret the response and why empty error fields must not be read as 'no errors'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads what is returned, then the legacy-name caveat, then usage guidance — a sensible order with no filler. There is mild redundancy between 'errorsObserved is false' and the later warning not to infer no errors, though the second occurrence serves a different (interpretive) purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description still explains the returned fields and their placeholder values, the filtering parameter, and the key interpretive pitfall. Combined with full schema coverage and safety annotations, an agent has everything needed to call and read this tool correctly.

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 coverage is 100% and both parameters are already well documented, including the advisory nature of maxAgeSeconds and the stale-snapshot behavior. The description only restates that logGroup filters names, adding no syntax or semantics beyond the schema; 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 and resource (returns CloudWatch log group names and retention metadata) with an explicit scope exclusion (without reading log events). It also disambiguates the misleading legacy name get_log_errors, so an agent can't mistake it for an error-diagnosis tool.

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

Usage Guidelines5/5

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

Gives an explicit positive trigger ('Call when checking retention policies') and explicit exclusions ('do NOT use to diagnose runtime errors or infer that no errors occurred'), plus guidance to use logGroup for filtering. Nothing about when to select or avoid this tool is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.