Skip to main content
Glama
yunusemregul

dynatrace-bridge-mcp

by yunusemregul
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

list_problems

Lists active and historical Dynatrace problems raised by Davis, filtered by status, severity, impact, entity, or time window, to show what is wrong now or what happened at a given time.

Instructions

Lists the problems Dynatrace (Davis) raised that were active in the time window: display id (P-…), internal problem id, title, severity, impact level, status, start, end, duration, root cause entity and how many entities were affected and impacted.

Filter by status (open / closed / all), impact_level (SERVICES, INFRASTRUCTURE, APPLICATION, ENVIRONMENT), severity (AVAILABILITY, ERROR, PERFORMANCE, RESOURCE_CONTENTION, CUSTOM_ALERT, …), entity_selector (e.g. entityId("SERVICE-1234567890ABCDEF") or type(HOST)) and text (case-insensitive, matched against id, title and entity names). An open problem that started before the window is included.

Start here for "what is wrong right now" or "what happened at that time". Follow up with get_problem (pass the P- id) for evidence, Davis root cause and the dependency path.

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
textNoCase-insensitive text matched against the display id, title, root cause and affected entity names.
limitNoMaximum number of problems to print. Default 25, at most 200. The output says how many were omitted.
statusNoopen, closed or all. Default all.
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.
severityNoOnly problems with this severity level.
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.
impact_levelNoOnly problems with this impact level.
entity_selectorNoDynatrace entitySelector; only problems that affect or impact these entities, e.g. `entityId("SERVICE-1234567890ABCDEF")`.
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.4/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 behavioral burden and does well: it discloses that execution goes through the Dynatrace Bridge browser extension in the user's logged-in browser, that a failure must be surfaced rather than worked around, that an open problem starting before the window is still included, and that truncation is reported ('The output says how many were omitted'). It does not cover permission requirements or rate/response-time behavior, so it falls short of a 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 ordered by importance: what it returns, how to filter, where to go next, then the execution caveat. Dense but front-loaded and free of filler; the returned-field enumeration is long, though it substitutes for a missing output schema and therefore earns its space.

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 10-parameter, read-only listing tool with no output schema, the description compensates by enumerating return fields, explaining the time-window resolution across time_from/time_to/minutes_lookback, covering the environment default and pointing at dynatrace_bridge_status for environment names. 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.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description largely restates filter semantics already documented per-parameter (status, impact_level, severity, entity_selector, text, time window), adding only the enumerated returned fields and a minor gloss on text matching that is slightly narrower than the schema's own wording ('id, title and entity names' vs. the schema's inclusion of root cause).

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 problems Dynatrace (Davis) raised that were active in the time window') and enumerates the exact fields returned, so the agent knows what it gets without opening a schema. It also distinguishes itself from the sibling get_problem, which is explicitly named as the follow-up for evidence.

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?

Gives an explicit entry-point instruction ('Start here for "what is wrong right now" or "what happened at that time"') plus the hand-off rule ('Follow up with get_problem (pass the P- id)'). Failure handling is also prescribed: report the error rather than falling back to browser automation.

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