Skip to main content
Glama
yunusemregul

dynatrace-bridge-mcp

by yunusemregul
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

pod_resources

Analyze Kubernetes pod and container CPU, memory, throttling, OOM kills, and restarts over time to diagnose why pods restart, get OOM-killed, or run slow.

Instructions

Shows the resource behaviour of the pods of a Kubernetes workload, or of one pod, over the time window: CPU usage, CPU throttling, memory (resident set per container, working set for the workload, usage in % of the limit), OOM kills and container restarts, per pod and per container, each as a summarised series (min / avg / max with its time / last / trend and a compact table over time).

Start here for "why does this pod restart / get OOM-killed / run slow": it opens with findings that flag obvious trouble: usage near the limit, significant CPU throttling, OOM kills, restarts inside the window, pods not running. Pass exactly one of workload or pod (id or name; find workloads with list_workloads). Narrow the window around a peak with time_from / time_to, then check pod_events for what Kubernetes did at that time and process_runtime for the JVM / Node.js view.

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
podNoA single pod, as an entity id (CLOUD_APPLICATION_INSTANCE-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.
workloadNoThe workload whose pods to analyse, as an entity id (CLOUD_APPLICATION-1234567890ABCDEF) or a name. A name that matches several entities returns the candidates instead of guessing.
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.
max_seriesNoMaximum containers summarised per metric, ranked by average. Default 10, at most 50.
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.6/5.0
Behavior4/5

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

No annotations, so the description carries the full burden and does so well: it discloses the output shape (findings plus summarised min/avg/max/last/trend series), the mutual-exclusivity constraint, and the unusual execution path (Dynatrace Bridge browser extension in the logged-in browser) with explicit failure handling guidance. It omits any payload-size or pagination caveats, but max_series in the schema partly covers that.

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 with purpose and the 'start here' triage signal, then parameters, then the execution caveat. It is dense and long for three paragraphs, but each paragraph has a distinct job (what it returns, when to use it, how it runs) and none 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?

With no output schema and 7 parameters, the description compensates by explaining the return format (findings plus per-pod/per-container summarised series) and the routing to sibling tools. An agent has everything needed to select and invoke it, including the browser-extension dependency and failure protocol.

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 the baseline is 3, but the description adds real meaning beyond the schema: the schema declares no required fields while the description states 'Pass exactly one of `workload` or `pod`', a constraint absent from the structured data. It also frames time_from/time_to as a way to narrow around a peak.

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+resource ('Shows the resource behaviour of the pods of a Kubernetes workload, or of one pod') and enumerates the exact metrics returned (CPU usage, throttling, RSS/working set, OOM kills, restarts). It is clearly distinguishable from sibling tools like pod_events and process_runtime, which it names as the next steps rather than duplicating.

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 says 'Start here for why does this pod restart / get OOM-killed / run slow', names the alternative tools to try afterwards ('pod_events', 'process_runtime'), and states the selection constraint 'Pass exactly one of `workload` or `pod`'. It even points to `list_workloads` for finding inputs.

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