Skip to main content
Glama
yunusemregul

dynatrace-bridge-mcp

by yunusemregul
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

read_settings

Read Dynatrace configuration (Settings 2.0) read-only: list schemas or inspect alerting, anomaly detection, and other settings at environment or entity scope, including effective values.

Instructions

Reads Dynatrace configuration (Settings 2.0), read-only: alerting profiles, anomaly detection thresholds, failure detection rules, request attributes, naming rules, maintenance windows and every other settings schema.

Without schema it lists the settings schemas; narrow the list with search (text matched against schema id and name, e.g. "alerting", "anomaly", "failure-detection"). With schema (e.g. builtin:alerting.profile) it prints the configured objects of that schema at scope (default environment; pass an entity id such as SERVICE-1234567890ABCDEF or HOST_GROUP-… for an entity-level override). Set effective: true to get the values actually in force at that scope, including inherited ones and defaults.

Values are printed as compact nested lists. Passwords, tokens, keys, credentials and anything else that looks like a secret are masked. The bridge cannot change settings.

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 settings objects (at most 50), or schemas when listing (default 50, at most 500) to print. Default 20. The output says how many were omitted.
scopeNoScope to read: `environment` (default) or an entity id, e.g. SERVICE-1234567890ABCDEF, HOST-…, PROCESS_GROUP-….
schemaNoSettings schema id, e.g. `builtin:alerting.profile`, `builtin:anomaly-detection.services`, `builtin:failure-detection-rulesets`. Omit to list the schemas.
searchNoWhen listing schemas: case-insensitive text matched against schema id and display name.
effectiveNoRead the effective values at the scope (inherited values and defaults included) instead of the objects stored at the scope. Default false.
max_linesNoMaximum lines printed per settings value. Default 40, at most 200.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.9/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: read-only ('The bridge cannot change settings'), secret masking, compact nested-list output format, and the browser-extension dependency with explicit failure handling. This is unusually rich behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, then organized by mode, then caveats. Every sentence earns its place: mode selection, scope, effective semantics, output/masking, and failure handling. No redundancy with the parameter list.

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-output-schema tool, the description supplies what's missing elsewhere: print format, masking, omission reporting, scope defaults, and the bridge failure protocol. An agent has everything needed to invoke it correctly.

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 already 100%, so the baseline is 3. The description nonetheless adds semantics the schema lacks, such as examples of schema ids, the meaning of entity-level overrides for `scope`, and what `effective: true` actually returns (inherited values and defaults).

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 ('Reads Dynatrace configuration (Settings 2.0)') and enumerates the categories covered (alerting profiles, anomaly detection thresholds, failure detection rules, etc.), which cleanly separates it from observability siblings like get_problem or query_metrics. The read-only scope is stated up front.

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?

Explicitly declares the two operating modes and the condition that selects each: without `schema` it lists schemas, with `schema` it prints configured objects at `scope`. It also explains narrowing via `search`, the `effective` flag behavior, and the fallback when the bridge fails ('report the error to the user; do not try 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