Skip to main content
Glama
yunusemregul

dynatrace-bridge-mcp

by yunusemregul
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

find_entities

Search Dynatrace entities by type, name, or selector to turn a name into the entity ID other tools need, or list services, hosts, pods, and more.

Instructions

Searches Dynatrace monitored entities of any type and returns their ids and names. Use it to turn a name the user mentions into the entity id that other tools need, or to list what exists (services, hosts, process groups, Kubernetes workloads, pods, containers, queues, …).

Give type (e.g. SERVICE, HOST, PROCESS_GROUP, PROCESS_GROUP_INSTANCE, CLOUD_APPLICATION (Kubernetes workload), CLOUD_APPLICATION_INSTANCE (pod), CONTAINER_GROUP_INSTANCE (container), KUBERNETES_CLUSTER, KUBERNETES_NODE, QUEUE) and optionally name (case-insensitive substring). For anything more specific pass a full Dynatrace selector (entitySelector syntax), e.g. type(CLOUD_APPLICATION_INSTANCE),fromRelationships.isInstanceOf(entityId("CLOUD_APPLICATION-1234567890ABCDEF")) for the pods of a workload, or type(SERVICE),tag("team:checkout"). Called with neither type nor selector, it lists the entity types that exist in the environment.

Only entities seen inside the time window are returned. Add fields (e.g. tags, managementZones, properties.cloudApplicationInstancePhase, fromRelationships.runsOn) for extra columns. Follow up with get_entity for all properties and relationships of one entity.

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
nameNoCase-insensitive substring of the entity name. Combined with `type`; ignored when `selector` is given.
typeNoEntity type, e.g. SERVICE, HOST, PROCESS_GROUP, PROCESS_GROUP_INSTANCE, CLOUD_APPLICATION (Kubernetes workload), CLOUD_APPLICATION_INSTANCE (pod), CONTAINER_GROUP_INSTANCE (container), KUBERNETES_CLUSTER, KUBERNETES_NODE, QUEUE. Ignored when `selector` is given.
limitNoMaximum number of entities (300 entity types when listing types) to print. Default 50, at most 500. The output says how many were omitted.
fieldsNoExtra entity fields to fetch and show as columns, e.g. ['tags', 'properties.cloudApplicationInstancePhase', 'fromRelationships.runsOn', 'lastSeenTms'].
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.
selectorNoFull Dynatrace entitySelector, used verbatim. Must contain a type(...) or entityId(...) criterion.
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.
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
Behavior3/5

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

No annotations are present, so the description must carry behavioral disclosure — and it does add real value: entities only inside the time window are returned, resolution goes through the Dynatrace Bridge browser extension, and on failure the agent is told to report the error rather than fall back to browser automation. It stops short of describing the output shape (there is no output schema, so return format is only partly inferred from the schema descriptions).

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 — purpose first, then parameter guidance, then behavior, then the failure-handling caveat. It is longer than strictly necessary (the type list is repeated almost verbatim in the schema), so it is efficient but not maximally tight.

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, all-optional search tool with no annotations and no output schema, the description covers the essentials: what is searched, what is returned (ids and names), time-window semantics, limit behavior with omitted counts, and the browser-extension dependency with failure guidance.

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 baseline is 3, but the description adds genuine semantic value: worked selector examples (pods of a workload, tagged services), a list of valid type values, and practical fields examples beyond the schema's list. It notably omits the interaction between selector and the other params except to say type/name are ignored.

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 ('Searches Dynatrace monitored entities of any type and returns their ids and names') and makes the differentiating role explicit: it converts a user-mentioned name into the entity id other tools need. It also distinguishes itself from the sibling get_entity by naming that tool as the follow-up for full properties.

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 when-to-use conditions ('turn a name the user mentions into the entity id', 'list what exists'), an explicit edge case (called with neither type nor selector, it lists entity types), and routes to the alternative get_entity for all properties and relationships.

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