Skip to main content
Glama
mnmozi

Dynatrace SaaS MCP Server

by mnmozi

preview_openpipeline_processor

Test a pipeline processor on sample data to validate its effect before applying to production configuration.

Instructions

Preview the effect of a pipeline processor on sample data without mutating any configuration (safe, read-only). Returns per-record match and transformed record results. Use this to author and validate processors before applying them with update_openpipeline_configuration. Include a 'sampleData' string field (JSON-encoded record) inside the processor definition.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
processorYesProcessor definition (type, matcher, fields, etc.). Include a 'sampleData' string field with a JSON-encoded record to test against, per the PreviewProcessorEnvelope spec. Example: { type: 'fieldsRename', sampleData: '{"hostname":"my-host"}', fields: [{ fromName: 'hostname', toName: 'host.name' }] }
Behavior4/5

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

Discloses read-only safety and return of per-record results. No annotations provided, so description carries full burden; lacks error condition details but sufficient for preview intention.

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?

Two concise sentences conveying purpose, guidance, and key instruction. No fluff, well-structured.

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?

Given no output schema, the description adequately explains return values and usage context. References the update tool for follow-up action.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

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

Schema coverage is 100%, and description adds value by emphasizing the sampleData field requirement within the processor object, including an example.

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?

Clearly states the tool previews processor effects safely without mutation, distinguishing it from the update tool. The verb 'Preview' + resource 'pipeline processor' is specific.

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 instructs to use this for authoring/validating before applying changes via update_openpipeline_configuration, and provides usage detail about including sampleData.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mnmozi/dynatrace-mcp-saas'

If you have feedback or need assistance with the MCP directory API, please join our Discord server