Skip to main content
Glama
yunusemregul

dynatrace-bridge-mcp

by yunusemregul
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

list_workloads

List Kubernetes workloads with namespaces, clusters, running versus desired pods, and CPU/memory usage against requests and limits to find workload IDs or spot pods near limits.

Instructions

Lists Kubernetes workloads (deployments, stateful sets, daemon sets, jobs; Dynatrace entity type CLOUD_APPLICATION) with workload type, namespace, cluster, running versus desired pods, and average CPU and memory usage against the configured requests and limits over the window.

Filter with name (case-insensitive substring), namespace (exact) and cluster (cluster name or KUBERNETES_CLUSTER id). Use it to find the workload id that list_pods, pod_resources, pod_events and process_runtime take, or to spot workloads running close to their limits.

This tool runs through the Dynatrace Bridge browser extension in the user's logged-in browser. If it fails, report the error to the user; do not try to open browser tabs or use browser automation instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoCase-insensitive substring of the workload name.
limitNoMaximum number of workloads to print. Default 25, at most 200. The output says how many were omitted.
clusterNoThe Kubernetes cluster, as an entity id (KUBERNETES_CLUSTER-1234567890ABCDEF) or a name. A name that matches several entities returns the candidates instead of guessing.
time_toNoAbsolute end time, ISO 8601; without a zone it is read as UTC. Without time_from, the window starts minutes_lookback before this. Must not be in the future.
namespaceNoKubernetes namespace, exact name (case-insensitive).
time_fromNoAbsolute start time, ISO 8601 (e.g. '2026-09-23T10:28:00Z'). A timestamp without a zone (Z or ±hh:mm) is read as UTC. Without time_to, the window runs from here to now. Must not be in the future.
environmentNoWhich Dynatrace environment to query, as named in the Dynatrace Bridge extension popup. Omit it for the default, the first environment configured there. The names are not listed here because the extension had not connected yet when this description was built; `dynatrace_bridge_status` lists them.
minutes_lookbackNoWindow length in minutes. Default 120. With neither time_from nor time_to it means the last N minutes up to now; with only time_to it means the N minutes ending at time_to; ignored when time_from is given. The response header always shows the resolved absolute UTC window.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and delivers non-obvious behavior: the tool runs through the Dynatrace Bridge browser extension in the user's logged-in browser, and on failure the agent should report the error rather than fall back to browser automation. It does not state permission/auth requirements, rate limits, or explicitly that it is a read-only operation, so it stops short of a 5.

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?

Three tight paragraphs: capability/returns first, filtering and usage second, transport caveat third. Every sentence carries information, with the most decision-relevant content front-loaded. Slightly long but not padded.

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?

No output schema exists, and the description compensates by detailing the returned fields (workload type, namespace, cluster, running vs desired pods, CPU/memory against requests and limits). With 8 optional params and a documented transport dependency, the main remaining gap is the absence of explicit auth/permission expectations.

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 schema already documents all 8 parameters including defaults, formats, and edge cases. The description restates filter semantics (case-insensitive substring name, exact namespace, cluster name or KUBERNETES_CLUSTER id) but adds nothing the schema does not already contain, so the 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 ('Lists Kubernetes workloads') and enumerates exactly which kinds (deployments, stateful sets, daemon sets, jobs) and the Dynatrace entity type. It also names what is returned (namespace, cluster, running vs desired pods, CPU/memory vs requests/limits), so an agent can distinguish it from sibling list tools without opening the schema.

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?

Explicitly names the sibling tools this feeds ('list_pods', 'pod_resources', 'pod_events', 'process_runtime') and the two conditions to reach for it (finding a workload id, spotting workloads near their limits). It also gives filter semantics (name substring, namespace exact, cluster name-or-id), leaving no inference about when to use 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