vmware-avi

Overview Schema Source Related Servers Score Discussions Admin

ako_logs

Read-onlyIdempotent

Retrieve AKO pod logs to diagnose Ingress creation failures, sync errors, and Controller connectivity issues. Returns raw log text for troubleshooting unhealthy pods or missing Ingresses.

Instructions

[READ] AKO pod logs — Ingress creation failures, sync errors, Controller connectivity.

Returns raw log text, not a table. Use when ako_status shows the pod unhealthy or ako_sync_diff reports a missing Ingress. Only the running container's logs are returned.

Input Schema

TableJSON Schema

Name	Required	Description
`tail`	No	Number of log lines (default 100).
`since`	No	Narrows the window, e.g. '30m', '1h'.
`context`	No	K8s context (optional, uses current).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.8.14Aug 31, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / context / description
```
Added value: +"K8s context (optional, uses current)."
```
- addedInput schema / properties / since / description
```
Added value: +"Narrows the window, e.g. '30m', '1h'."
```
- addedInput schema / properties / tail / description
```
Added value: +"Number of log lines (default 100)."
```

Changed1 schema field changedv1.5.38Jun 12, 2026

addedInput schema / properties / context

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Context"
+}

Addedv1.5.29May 29, 2026
Removedv1.5.28May 24, 2026
First observedv1.5.22May 11, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the safety profile is covered. The description adds valuable behavioral context beyond annotations: 'Returns raw log text, not a table' and 'Only the running container's logs are returned,' which alerts the agent to output format and scope limitations. No contradiction with annotations.

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?

The description is three short, purposeful sentences. It front-loads the tool's purpose, states the return format, gives usage triggers, and notes a scope limitation. Every sentence earns its place with no filler.

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?

For a read-only log retrieval tool, the description covers purpose, trigger conditions, return format, and container scope. Combined with rich annotations, a full parameter schema, and an output schema, nothing essential is missing for an agent to select and invoke 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 description coverage is 100%, so the parameter meanings are already fully documented. The description does not add parameter-specific guidance (e.g., how tail/since/context interact), but because the schema covers all parameters with defaults and examples, baseline 3 is appropriate.

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?

The description opens with '[READ] AKO pod logs' and specifies concrete use cases: 'Ingress creation failures, sync errors, Controller connectivity.' It also distinguishes the tool from table-returning siblings by stating 'Returns raw log text, not a table,' so an agent can disambiguate from tools like vs_error_logs or ako_status.

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 explicit trigger conditions: 'Use when ako_status shows the pod unhealthy or ako_sync_diff reports a missing Ingress.' This names sibling tools as decision points and provides clear context. However, it does not state when not to use this tool or name alternatives beyond the implied conditions.

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