Skip to main content
Glama
yunusemregul

dynatrace-bridge-mcp

by yunusemregul
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

memory_allocation_hotspots

Find where a Dynatrace process group allocates memory to diagnose high GC time or memory growth; use survivors only to spot leak candidates.

Instructions

Shows where a process group allocates memory (Dynatrace continuous memory profiling, Java): total allocated and surviving bytes, allocation per API, the methods that allocate the most with their main callers and object types, and the most allocated types.

Use it for high garbage-collection time or memory growth. survivors_only: true restricts to objects that survived a garbage collection (candidates for leaks and heap growth). The default window is the last 15 minutes because Dynatrace answers with a very large call tree for busy process groups; keep the window short. When memory profiling is not enabled or not supported for the process group, or the answer is too large to relay, the tool says so and what to do. cpu_by_process_group lists memory for the process groups that support it.

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 allocating methods and types to print. Default 15, at most 100. 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.
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.
survivors_onlyNoOnly objects that survived a garbage collection. Default false.
minutes_lookbackNoWindow length in minutes. Default 15. 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
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 discharges it: it explains why the default window is 15 minutes (large call trees for busy process groups), what happens when profiling is unavailable ('the tool says so and what to do'), and an operational constraint — it runs through the Dynatrace Bridge extension in the user's logged-in browser, and on failure the agent must report the error rather than use browser automation.

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 what the tool returns, then usage triggers, then caveats and the browser-extension constraint in short, scannable paragraphs. The opening sentence is a long run-on listing output sections, but every sentence still carries information an agent needs.

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 7-parameter, no-annotation, no-output-schema tool, the description covers output shape, failure modes with remediation, environment resolution, and an operational constraint — everything needed to call it correctly and interpret its outcome.

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 semantic value beyond the schema: it frames 'survivors_only' as leak/heap-growth candidates and explains the 15-minute default as a deliberate size-management choice. Time-window semantics and the environment default are left to the schema.

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?

Specific verb+resource ('Shows where a process group allocates memory') with the exact output sections enumerated (allocated/surviving bytes, allocation per API, top methods with callers and object types, most allocated types). This is clearly distinguishable from siblings like method_hotspots and cpu_by_process_group, which cover different signal types.

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?

Explicit trigger conditions are given: 'high garbage-collection time or memory growth', plus 'survivors_only: true' for leak/heap-growth candidates. It also points to cpu_by_process_group to discover which process groups support memory profiling. It stops short of naming a rival tool to prefer for adjacent questions, hence 4 rather than 5.

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