Skip to main content
Glama
Sign In
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_crm_chart

Read-onlyIdempotent

Read a saved or unpublished system chart or personal chart definition by ID and scope to inspect its configuration without publishing it.

Instructions

Read a system saved/unpublished or personal chart definition; does not establish runtime publication.

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": {
      "scope": "<scope>",
      "id": "<id>"
    },
    "name": "get_crm_chart"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
scopeYes
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.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds one genuine behavioral fact — that reading does not establish runtime publication — but says nothing about what happens when the id is unknown or the scope does not match the chart's actual owner, which is the main failure mode for a scoped lookup.

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?

A single front-loaded sentence with a semicolon qualifier; every clause carries information and there is 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.

Completeness3/5

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

For a simple three-parameter read with annotations covering safety and no output schema, the definition is close to sufficient. The remaining gap is that nothing indicates what a returned 'chart definition' contains or how to tell a system chart from a personal one when the id is valid but out of scope.

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 33%: environment_profile is documented in the schema while id (GUID pattern) and scope (enum) carry only structural constraints. The description partially compensates by mapping 'system saved/unpublished' and 'personal' onto the scope enum, but adds nothing about the id or environment_profile semantics.

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 ('Read') and resource ('chart definition'), and disambiguates scope by naming both 'system saved/unpublished' and 'personal' variants. It does not name the sibling it contrasts with (list_crm_charts, change_crm_chart), but the read-a-single-chart framing is unambiguous.

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 'does not establish runtime publication' clause implicitly separates this read from any publish action, and 'saved/unpublished' implies a state constraint. However, it never explicitly says when to use this versus list_crm_charts or change_crm_chart, so the agent must infer the routing from the names.

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