Skip to main content
Glama
yunusemregul

dynatrace-bridge-mcp

by yunusemregul
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_dashboard

Read a Dynatrace dashboard's owner, tags, tiles, and chart metric selectors; optionally run tile queries over a time window to inspect summarized series.

Instructions

Shows one Dynatrace dashboard: owner, tags and every tile with its type and title, and for chart (Data Explorer) tiles the metric selectors behind them, so the same data can be read with query_metrics.

dashboard is an id from list_dashboards or a name (an ambiguous name returns the candidates). Reading the queries of a chart tile costs one request to Dynatrace per tile, so only the first tile_details chart tiles (12 by default, at most 30) get their queries; the others are listed without them, and the output names the tile ids to pass as tile to read those next. run_queries: true executes up to max_queries of the tile selectors over the time window and prints each as summarised series.

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
tileNoTile ids (from the tiles table) whose queries to read, at most 30 per call. The table then lists only these tiles. Default: the first `tile_details` chart tiles in reading order.
limitNoMaximum number of tiles in the table to print. Default 60, 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.
dashboardYesDashboard id (UUID from `list_dashboards`) or name.
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.
max_queriesNoMaximum number of tile queries to run with `run_queries`. Default 5, at most 20.
run_queriesNoAlso run the tile metric selectors and print summarised series. Default false.
tile_detailsNoHow many chart tiles get their queries read when `tile` is not given; each costs one request to Dynatrace. Default 12, at most 30.
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.8/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 well: it discloses the per-tile request cost to Dynatrace, the default/maximum tile_details budget (12 default, at most 30), that remaining tiles are listed without queries and their ids returned for a follow-up call, and that execution runs through the Dynatrace Bridge browser extension in the logged-in browser. This is exactly the operational context an agent needs.

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-loads what the tool returns in the first sentence, then devotes the second paragraph to the token-cost mechanics and the browser-extension dependency. It is dense but every sentence earns its place; slightly long given the parameter volume.

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?

Ten parameters, no annotations, and no output schema, yet the description explains the return shape, the tile budget semantics, the follow-up call path, the time-window behavior, and the failure mode. Nothing material 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% and the property descriptions are already detailed, so baseline is 3. The description adds value beyond the schema by explaining cross-parameter relationships, e.g. that `tile` overrides the default first-`tile_details` chart tiles and that the output names the tile ids to pass as `tile` next.

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+resource ('Shows one Dynatrace dashboard') and enumerates exactly what is returned: owner, tags, every tile with type and title, and metric selectors for chart tiles. It explicitly distinguishes itself from siblings by pointing to `list_dashboards` for ids and `query_metrics` for reading the underlying data.

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 concrete conditions: `dashboard` accepts an id from `list_dashboards` or a name (ambiguous names return candidates); `tile` selects which tiles' queries to read; `run_queries: true` executes the selectors. It names `query_metrics` as the alternative for reading the same data and instructs what to do on failure (report the error, do not fall 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