Skip to main content
Glama
Sign In
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

delete_note_attachments

Destructive

Preview and delete 1–10 note attachments with optimistic concurrency and per-item ETags; operations run sequentially and stop on first failure without retry.

Instructions

Preview then delete 1–10 attachments with native optimistic concurrency and individual ETags. Sequential non-atomic operation stops on failure; no automatic retry.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ids": "<ids>"
    },
    "name": "delete_note_attachments"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes
dry_runNo
expected_hashNo
environment_profileNoOptional named environment profile for this call; omit to use the configured default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.2

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already mark the tool as destructive and non-idempotent, and the description adds useful operational context: native optimistic concurrency, individual ETags, sequential non-atomic execution, stop-on-failure behavior, and no automatic retry. This goes meaningfully beyond the annotations without contradicting them.

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 two dense sentences with no wasted wording, and the preview-then-delete behavior is front-loaded. The operational caveats are packed efficiently without obscuring the main purpose.

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

Completeness3/5

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

For a destructive batch-delete tool with no output schema and low schema coverage, the description covers important safety and failure behavior. It still leaves gaps around result reporting, per-attachment ETag semantics, and the environment_profile parameter.

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 description coverage is only 25%, so the description carries more burden than usual. It clarifies the 1–10 attachment limit and the preview/dry-run concept, and hints at ETag-based concurrency, but it does not explain expected_hash or environment_profile in detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific verb and resource: deleting note attachments, with a 1–10 item scope and preview capability. It is distinguishable from sibling upload/list/download tools, though it does not explicitly name those alternatives.

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

Usage Guidelines3/5

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

It implies a preview-then-delete workflow and notes that the operation stops on failure with no retry. However, it does not explicitly state when to use this tool versus list_note_attachments, download_note_attachments, or upload_note_attachments.

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