Skip to main content
Glama
Sign In
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_note_attachments

Read-onlyIdempotent

List visible note attachments for a parent record to inspect attachment metadata without reading file content; results are marked when limited.

Instructions

List visible CRM note attachments for a parent record without reading attachment content. A limited result is explicitly marked.

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": {
      "parent_id": "<parent_id>"
    },
    "name": "list_note_attachments"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNo
parent_idYes
environment_profileNoOptional named environment profile for this call; omit to use the configured default.
parent_logical_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.2

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), yet the description adds genuine context beyond them: results are visibility-filtered ('visible') and truncated results are explicitly signalled. It does not say how truncation is marked or whether the parent record's existence affects the result, which keeps it short of a 5.

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 short sentences, no filler, with the core action and its non-obvious constraint front-loaded before the truncation caveat. Nothing could be removed without losing information.

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 four-parameter read tool with no output schema, the description covers the action and one behavioral caveat but leaves the parent_id/parent_logical_name relationship and the meaning of 'top' unresolved. An agent could still call it (parent_id is required and unambiguous enough), but not confidently for the optional parameters.

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

Parameters2/5

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

Schema coverage is only 25%, so the description must compensate, and it largely does not. The critical ambiguity between parent_id (a required GUID by pattern) and parent_logical_name is never explained, and 'top' is only obliquely referenced via 'a limited result is explicitly marked' rather than described as a page-size cap.

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?

States a specific verb and resource ('List visible CRM note attachments') plus a scope ('for a parent record'), and the phrase 'without reading attachment content' implicitly separates it from download_note_attachment(s)/delete_note_attachments. It does not name a sibling outright, so an agent must infer the boundary rather than be told it.

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 'without reading attachment content' clause implies enumeration-before-download usage, but there is no explicit when-to-use or when-not-to-use statement and no alternative named. The agent can guess this is the discovery step preceding download_note_attachments, but the description never says so.

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