Skip to main content
Glama
Sign In
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

download_note_attachments

Downloads 1-10 Dynamics 365 note attachments to separate absolute local paths without overwriting existing files and reports completed items if a batch stops.

Instructions

Download 1–10 note attachments to distinct absolute local paths without overwriting existing files; reports completed items if the batch stops.

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": {
      "files": "<files>"
    },
    "name": "download_note_attachments"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesYes
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

A4.1/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, so the safety profile is already carried; the description adds genuinely new behavior: no overwriting of existing files, paths must be distinct and absolute, and partial-batch failure reports completed items. It does not address permission requirements, whether parent directories are created, or rate limits.

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?

One dense sentence that front-loads the action, then the batch limit, then the path constraints, then the failure semantics. No filler or restatement of the tool name.

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

Completeness4/5

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

For a batch write-to-disk tool with no output schema, the definition covers cardinality, path rules, overwrite protection, and partial-failure reporting, which is most of what an agent needs. Remaining gaps are edge behaviors such as missing parent directories and the shape of the completion report.

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 50% and the undocumented "files" array is compensated well: the description supplies the 1–10 cardinality and, critically, the absolute-path and distinct-path constraints on output_path that the schema's bare string type does not convey. Combined with the schema's existing UUID pattern and environment_profile note, the caller has what it needs.

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?

"Download 1–10 note attachments to distinct absolute local paths" states a specific verb, resource, and batch scope, which implicitly separates it from the singular download_note_attachment sibling. It does not explicitly name or contrast with that sibling, so differentiation is inferred from the plural name rather than stated.

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?

The 1–10 batch bound implies this is the multi-item path versus the single-attachment sibling, but the description never says when to choose one over the other or that attachments must first be enumerated via list_note_attachments. Usage is implied rather than directed.

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