Skip to main content
Glama
yunusemregul

dynatrace-bridge-mcp

by yunusemregul
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

cpu_by_process_group

Identify process groups with high CPU consumption in a time window, showing CPU time, share, GC time, and peak timing to diagnose performance issues.

Instructions

Lists the process groups that consumed the most CPU in the window (Dynatrace continuous CPU profiling): CPU time, share of the total, CPU time spent in garbage collection, when the peak was, and which deeper analyses each process group supports.

Start here for "which process burns the CPU". Follow up with method_hotspots (hot methods), thread_analysis (thread groups and states) or memory_allocation_hotspots, passing the PROCESS_GROUP id from the table as process_group. For CPU per endpoint use trace_statistics with metric: "CPU_TIME".

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
textNoOnly process groups whose name, id or technology contains this text (case-insensitive).
limitNoMaximum number of process groups to print. Default 20, at most 200. The output says how many were omitted.
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.
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.7/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses the runtime dependency (executes through the Dynatrace Bridge browser extension in the user's logged-in browser), an explicit failure protocol (report the error, do not open tabs or automate), and output behavior (limit default 20 / max 200, omitted rows are reported, resolved UTC window shown in the header). This is materially more than the schema provides.

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?

Front-loaded with the core purpose, then discovery routing, then environment/failure caveat. Each of the three short paragraphs carries distinct, non-redundant information 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?

No output schema exists, yet the description describes what the table contains (CPU time, share of total, GC time, peak timing, supported deeper analyses) and how omissions are surfaced. Combined with the browser-extension caveat and the explicit routing to follow-up tools, an agent has everything needed to call and interpret it.

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 all six parameters (text, limit, time_to, time_from, environment, minutes_lookback) are already documented in the schema, including the ISO-8601/UTC handling and lookback semantics. The description adds only the cross-tool note about passing the process group id downstream, which is about the consumer tool, not this one's parameters. Baseline 3 is correct.

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 the process groups that consumed the most CPU in the window') and immediately scopes it to Dynatrace continuous CPU profiling. It also enumerates the returned metrics, so an agent can tell it apart from sibling tools like method_hotspots or trace_statistics without opening a 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 says when to start here ('which process burns the CPU') and names three follow-up alternatives (method_hotspots, thread_analysis, memory_allocation_hotspots) plus a distinct route for per-endpoint CPU (trace_statistics with metric CPU_TIME). It even specifies the handoff value: pass the PROCESS_GROUP id as process_group.

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