Skip to main content
Glama
mnmozi

Dynatrace SaaS MCP Server

by mnmozi

update_self_notification

Update a Dynatrace self-notification by providing its UUID and the full notification definition. Modifies an existing notification configuration.

Instructions

Update a self-notification by ID (WRITE, platform notification v1).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesSelf-notification UUID.
notificationYesNotification definition object. Pass all required fields per the notification spec.
Behavior2/5

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

The description labels the tool as 'WRITE' but does not disclose whether the update is partial or full replacement, how missing fields are handled, or any constraints. No annotations are present to supplement this lack of detail.

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?

The description is a single concise sentence that front-loads the action and resource, with no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with a nested object parameter and no output schema, the description lacks essential context such as update semantics, required fields in the notification object, and any constraints. This is insufficient for safe agent invocation.

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 coverage is 100% with descriptions for both parameters ('Self-notification UUID' and 'Notification definition object'). The description adds no additional meaning beyond what the schema provides.

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?

The description explicitly states 'Update a self-notification by ID', specifying the verb and resource. It distinguishes this tool from siblings like create_self_notification and delete_self_notification.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus creating or deleting self-notifications. The agent has no context for choosing the correct operation.

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