Skip to main content
Glama
yunusemregul

dynatrace-bridge-mcp

by yunusemregul
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

list_events

Lists Dynatrace events like deployments, process restarts, and Kubernetes failures in a time window, so you can see what changed around an incident.

Instructions

Lists Dynatrace events in a time window: deployments, process restarts, Kubernetes events (probe failures, kills, scheduling), availability and anomaly events (error rate or response time increase, CPU saturation), custom info and annotations. Identical events (same type, title, entity and Kubernetes reason) are collapsed into one row with a count and the first and last time, so a flapping probe is one line.

Scope it with entity_selector (entitySelector syntax, e.g. entityId("SERVICE-1234567890ABCDEF"), type(CLOUD_APPLICATION_INSTANCE),fromRelationships.isInstanceOf(entityId("CLOUD_APPLICATION-1234567890ABCDEF")) for the pods of a workload, type(HOST)), event_type (e.g. CUSTOM_DEPLOYMENT, PROCESS_RESTART, SERVICE_ERROR_RATE_INCREASED, CUSTOM_INFO) and status (open / closed). event_selector takes a raw Dynatrace eventSelector instead, e.g. property.dt.kubernetes.event.reason("Unhealthy"). Without any filter it lists every event of the environment in the window.

Use it to answer "what changed" around the time something broke; then get_entity or service_overview on an entity id, or list_problems for the same window.

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 event groups to print. Default 30, at most 200. The output says how many were omitted.
statusNoOnly events that are still open, or only closed ones. Default: both.
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.
event_typeNoEvent type, e.g. CUSTOM_DEPLOYMENT, CUSTOM_INFO, PROCESS_RESTART, SERVICE_ERROR_RATE_INCREASED, SERVICE_SLOWDOWN, MARKED_FOR_TERMINATION.
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.
event_selectorNoRaw Dynatrace eventSelector, used verbatim instead of `event_type` and `status`.
entity_selectorNoDynatrace entitySelector limiting the entities the events belong to, e.g. `entityId("HOST-1234567890ABCDEF")` or `type(SERVICE),entityName.contains("checkout")`.
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
Behavior5/5

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

No annotations exist, so the description carries the full burden and does so: it discloses the deduplication rule (identical type/title/entity/K8s reason collapsed into one row with count and first/last time), the unfiltered default (every event in the window), and the browser-bridge execution constraint with explicit failure handling ('report the error to the user; do not try to open browser tabs').

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?

Well front-loaded: what is listed and how events collapse come first, then scope, then routing, then the bridge caveat. It is long, and some scoping detail duplicates schema descriptions that already carry examples, but nearly every sentence adds a distinct fact.

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 9-parameter tool with no annotations and no output schema, the description covers what the tool returns (grouped rows with counts and first/last timestamps, resolved UTC window in the header, omitted-count reporting) and how it executes. Nothing an agent needs to call it correctly 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 coverage is 100%, so the baseline is 3, but the description goes beyond the schema with composite entitySelector examples (fromRelationships.isInstanceOf for workload pods), a raw eventSelector example, and the interaction semantics of event_selector overriding event_type/status. That is real added meaning over the already-documented parameters.

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 Dynatrace events) plus the event taxonomy it covers — deployments, restarts, Kubernetes, availability/anomaly, custom info — and names the distinguishing scoping fields. An agent can tell it apart from list_problems and get_entity without opening any 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?

Explicitly frames the use case ('what changed' around a breakage) and routes to the right follow-ups (get_entity, service_overview, list_problems for the same window). It stops short of an explicit exclusion, e.g. when to prefer pod_events for pod-scoped Kubernetes events, so it is clear context rather than full when/when-not coverage.

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