Skip to main content
Glama
vish288

mcp-argocd

by vish288
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Argocd Get Pod Logs

argocd_get_pod_logs
Read-onlyIdempotent

Fetch container logs from an Argo CD application's pods to troubleshoot issues. Filter by app, pod, container, namespace, tail lines, or previous instance.

Instructions

Get container logs (never follows). Returns lines with pod and timestamp, the pods seen, and a shown_lines count; stops at the stream's last marker.

Input Schema

NameRequiredDescriptionDefault
kindNoOwner kind, e.g. Deployment
nameYesApplication name; accepts namespace/name for apps-in-any-namespace
groupNoOwner API group
filterNoOnly lines containing this string
projectNoProject; with it a missing app is 404 and a wrong-project app is 403
pod_nameNoPod name; or pass kind + resource_name
previousNoLogs from the previous container instance
containerNoContainer name
namespaceNoPod namespace
match_caseNoCase-sensitive filter
tail_linesNoLines from the tail (1-1000)
app_namespaceNoOverride appNamespace; defaults to ARGOCD_APP_NAMESPACE
resource_nameNoOwner resource name
since_secondsNoOnly logs newer than N seconds

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.4.0
    • changedInput schema / properties / tail_lines / description
      Previous value: -"Lines from the tail (0-1000)"New value: +"Lines from the tail (1-1000)"
    • changedInput schema / properties / tail_lines / minimum
      Previous value: -0New value: +1
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "type": "object",
-  "x-fastmcp-wrap-result": true
-}New value: +null
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish readOnly/idempotent/openWorld, but the description adds real behavioral value beyond them: it discloses the return shape (per-line pod + timestamp, pods seen, shown_lines count) and the termination behavior ('stops at the stream's last marker', never follows). That materially helps an agent interpret results and avoid expecting a live stream.

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 tight sentences, front-loaded with the verb and the most important constraint ('never follows'), then the return format. No filler; every clause earns its place.

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 14-parameter read tool with no output schema, the description usefully compensates by describing the returned structure and the stream-termination behavior, while annotations cover safety. What remains thin is routing/selection guidance, but the core call contract is 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 coverage is 100% across 14 well-described parameters, so the schema carries the semantics. The description adds no parameter-level meaning (nothing on filter, tail_lines, previous, since_seconds, or pod_name vs kind+resource_name selection), so baseline 3 applies.

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?

Clear specific verb+resource: 'Get container logs (never follows)'. The parenthetical immediately delimits scope (snapshot, not streaming). It does not explicitly distinguish from sibling tools, but no sibling in the list retrieves pod logs, so ambiguity is low.

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 explicit when-to-use guidance, no named alternatives, no prerequisites. The 'never follows' clause implies a non-streaming snapshot, but the agent is not told when this is preferable to any other log/observability path, nor what conditions select it.

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