Skip to main content
Glama
This connector has been deprecated

Replaced by Control Plane.

This listing has been renamed. Control Plane is now listed as com.controlplane/mcp.

It is the same server at the same endpoint (https://mcp.cpln.io/mcp), so existing connections keep working. Please use the new listing going forward.

Get Workload Logs

get_workload_logs
Read-onlyIdempotent

Query the logs of workloads in a GVC (gvc, workload, container, location) or of an mk8s cluster with the logs add-on (cluster, namespace, pod, container, node, job), OR pass a raw LogQL query, which REPLACES the structured params, so it must embed ALL labels itself. Workload labels: gvc, workload, container, location, provider, replica, stream (replica and stream only via a raw query). Cluster labels: cluster_name, namespace, pod, container, node, job; Control Plane workloads on a cluster log under their gvc. filter is a literal substring match (|=), not regex; for regex use a raw query with |~. Cron run logs: scope a raw query by the replica from list_deployments jobExecutions.

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_workload_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoAbsolute end time (exclusive, ISO 8601).
gvcNoGVC name. Required unless `cluster` or a raw `query` is provided.
jobNoWith `cluster`: log source (all when omitted).
orgNoOrganization slug.
podNoWith `cluster`: pod name.
fromNoAbsolute start time (inclusive, ISO 8601). Overrides `since`. Must be earlier than `to`.
nodeNoWith `cluster`: node name.
limitNoMaximum log entries to return (default: 30, max: 999).
orderNoSort order (default: "oldest_first").
queryNoRaw LogQL query. REPLACES the structured params entirely, so it must embed ALL labels itself (gvc, workload, location, …) — required for the replica/stream labels, which have no structured param. Not sanitized — use structured params when possible.
sinceNoLookback window as relative duration (default: "1h"). Examples: "30m", "2h", "1d".
filterNoLiteral substring filter (LogQL `|=`) — only return log lines containing this exact text. NOT a regex; for regex matching use a raw `query` with `|~`.
clusterNomk8s cluster name, in place of `gvc`: the cluster's own logs (logs add-on).
locationNoLocation to filter logs for (e.g., "aws-us-east-1").
workloadNoWorkload name to filter logs for.
containerNoContainer name to filter logs for (e.g., "main", "_accesslog").
namespaceNoWith `cluster`: Kubernetes namespace.

Output Schema

NameRequiredDescriptionDefault
okYes
dataNoThe full result. Read this, not only the summary.
detailsNo
summaryYes
nextStepsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / cluster
      Added value: +{
      +  "description": "mk8s cluster name, in place of `gvc`: the cluster's own logs (logs add-on).",
      +  "type": "string"
      +}
    • changedInput schema / properties / gvc / description
      Previous value: -"GVC name. Required unless raw `query` is provided."New value: +"GVC name. Required unless `cluster` or a raw `query` is provided."
    • addedInput schema / properties / job
      Added value: +{
      +  "description": "With `cluster`: log source (all when omitted).",
      +  "enum": [
      +    "kubernetes-pods",
      +    "kubelet",
      +    "kernel",
      +    "docker-containers",
      +    "audit"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / namespace
      Added value: +{
      +  "description": "With `cluster`: Kubernetes namespace.",
      +  "type": "string"
      +}
    • addedInput schema / properties / node
      Added value: +{
      +  "description": "With `cluster`: node name.",
      +  "type": "string"
      +}
    • addedInput schema / properties / pod
      Added value: +{
      +  "description": "With `cluster`: pod name.",
      +  "type": "string"
      +}
  2. Changed23 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / container / minLength
      Removed value: -1
    • removedInput schema / properties / from / maxLength
      Removed value: -40
    • removedInput schema / properties / gvc / minLength
      Removed value: -1
    • removedInput schema / properties / location / minLength
      Removed value: -1
    • changedInput schema / properties / org / description
      Previous value: -"Organization slug (lowercase kebab-case). NEVER guess — if the user has not named one, ask. On org-not-found, stop and ask; do not retry variants."New value: +"Organization slug."
    • removedInput schema / properties / org / maxLength
      Removed value: -63
    • removedInput schema / properties / org / minLength
      Removed value: -1
    • removedInput schema / properties / org / pattern
      Removed value: -"^[a-z0-9]([a-z0-9-]{0,61}[a-z0-9])?$"
    • removedInput schema / properties / query / maxLength
      Removed value: -500
    • removedInput schema / properties / query / minLength
      Removed value: -1
    • removedInput schema / properties / since / maxLength
      Removed value: -20
    • removedInput schema / properties / to / maxLength
      Removed value: -40
    • removedInput schema / properties / workload / minLength
      Removed value: -1
    • removedInput schema / required
      Removed value: -[
      -  "org"
      -]
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedOutput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / properties / data / description
      Previous value: -"The full machine-readable result — list rows, the resource object, query results. Read THIS, not just the summary."New value: +"The full result. Read this, not only the summary."
    • addedOutput schema / properties / details
      Added value: +{
      +  "type": "string"
      +}
    • removedOutput schema / properties / nextSteps / description
      Removed value: -"Recommended follow-up actions for this task, in order."
    • removedOutput schema / properties / ok / description
      Removed value: -"Whether the call succeeded."
    • removedOutput schema / properties / summary / description
      Removed value: -"One-line summary of the result."
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description's job is to add operational context — and it does: a raw `query` REPLACES all structured params (a real footgun), the query is explicitly 'Not sanitized', and `from` overrides `since`. It adds little about result volume or rate limiting beyond what the `limit` schema already says.

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-loaded and dense: mode selection comes first, then label sets, then the filter/query caveats, then the cron edge case. Slight redundancy in re-listing label names (gvc, workload, container, location) that duplicate the schema descriptions, and the parenthetical lists make it read as a run-on, but no sentence is 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 17-parameter tool with an output schema, this covers what the schema cannot: mode selection, parameter-replacement precedence, regex-vs-literal filtering, control-plane workload labeling, and cron log scoping. Timestamps, ordering, limits, and return shape are fully handled by the schema and output schema respectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds genuine cross-parameter meaning the schema cannot express: precedence between `query` and the structured params, `from` overriding `since`, which labels have no structured equivalent (replica, stream), and the exact sense of `filter` as `|=` not regex. The A-or-B relationship between `gvc` and `cluster` is only partially restated from the schema.

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?

Specific verb+resource ('Query the logs of workloads') with three clearly delineated modes: GVC structured params, mk8s cluster params, or a raw LogQL query. It is unambiguous what the tool retrieves, but it never distinguishes itself from log-adjacent siblings such as query_audit_events, query_metrics, or query_traces, so an agent must infer that boundary from the word 'logs' alone.

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?

Gives clear routing rules: use structured params when possible, switch to a raw `query` only when you need replica/stream labels or regex, and use `filter` for literal substring matching rather than `|~`. It also points to `list_deployments` jobExecutions to scope cron run logs. It stops short of stating when not to use this tool at all (e.g., versus metrics/traces/audit events).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.