Skip to main content
Glama
yunusemregul

dynatrace-bridge-mcp

by yunusemregul
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

thread_analysis

Analyze thread states and CPU usage of a process group to diagnose CPU-bound, lock contention, or I/O blocking; filter by state and rank thread groups by CPU.

Instructions

Analyses the threads of a process group (Dynatrace continuous thread analysis): how many threads are in each state (running, locking, network I/O, disk I/O, optionally waiting), and the thread groups ranked by CPU time with their average thread count and state samples.

Use it to see whether a process is CPU-bound, blocked on locks or stuck in I/O, and which thread pool is responsible. state keeps only thread groups seen in that state and ranks by it (e.g. LOCK for lock contention). Follow up with method_hotspots on the same process group for the methods.

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
limitNoMaximum number of thread groups to print. Default 20, at most 200. The output says how many were omitted.
stateNoOnly thread groups sampled in this state, ranked by its samples. Default: all, ranked by CPU time.
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.
process_groupYesThe process group, as an entity id (PROCESS_GROUP-1234567890ABCDEF) or a name. A name that matches several entities returns the candidates instead of guessing.
include_waitingNoAlso include waiting (idle) threads. Default false.
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 does well: it discloses the browser-bridge execution dependency, instructs the agent to report rather than work around failures, and explains ranking behavior ('ranked by its samples' vs 'ranked by CPU time'). It does not cover permissions, rate limits, or result-size behavior, keeping it at 4 rather than 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 short paragraphs, front-loaded with purpose, then usage, then the environment caveat. Every sentence carries information, though the browser-bridge paragraph is slightly verbose relative to the rest.

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 an 8-parameter tool with 100% schema coverage and no output schema, the description supplies the missing operational context: process-group name resolution ambiguity, environment defaults tied to dynatrace_bridge_status, and the bridge execution model. Only a brief note on expected result scope is missing.

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 description coverage is 100%, so baseline is 3. The description goes beyond the schema by explaining the state filter's semantics and giving a concrete enum usage example ('LOCK for lock contention') that the schema enum alone doesn't convey, and clarifying that output states how many groups were omitted.

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 ('Analyses the threads of a process group'), names the underlying capability (Dynatrace continuous thread analysis), and enumerates what the output contains (state counts, thread groups ranked by CPU time). An agent can distinguish this from siblings like cpu_by_process_group or method_hotspots 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit diagnostic scenarios ('see whether a process is CPU-bound, blocked on locks or stuck in I/O') and an example of when to use the state filter ('LOCK for lock contention'), plus a named follow-up tool for methods. It stops short of stating when NOT to use this versus the sibling process tools, which is the only gap.

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