mcp-dynamics-365

get_entity

Retrieve a specific Dynamics 365 entity record by its unique ID. Specify the entity set and record GUID to fetch selected fields for CRM data access.

Instructions

Get a specific entity record by ID from Dynamics 365

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": {
      "entitySet": "<entitySet>",
      "entityId": "<entityId>"
    },
    "name": "get_entity"
  }
}

Input Schema

Name	Required	Description
`select`	No	Comma-separated list of fields to retrieve (e.g., "firstname,lastname,emailaddress1")
`entityId`	Yes	The unique identifier (GUID) of the entity record
`entitySet`	Yes	Entity set name (plural form, e.g., "contacts", "accounts", "opportunities")

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0Sep 13, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden, and 'Get' only weakly implies a read operation. It does not state that the call is non-mutating, what happens when the ID does not exist (empty vs error), or any permission/scope requirements for the Dynamics 365 entity set.

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 no filler; the verb and lookup key lead the sentence and nothing is repeated from the schema.

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 tool with fully documented parameters, the definition is minimally viable, but it omits what the returned record looks like and how 'select' affects the response, which matters because there is no output schema.

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 100%, including the comma-separated format and example for 'select' and the plural-form guidance for 'entitySet', so the baseline is 3. The description adds nothing beyond the schema, mentioning only the ID lookup.

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 (Get), resource (entity record), lookup key (by ID), and source system (Dynamics 365), so an agent can distinguish it from list_entities and query_entities at a glance. It stops short of explicitly naming those siblings or the conditions that would route to them.

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?

The description gives no when-to-use guidance: nothing about preferring this over query_entities/execute_odata_query when a filter or multiple records are needed, and no prerequisite or fallback behavior if the ID is unknown. The 'by ID' phrasing implies single-record retrieval but does not state an alternative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server