Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

get_entity_navigation_links

Retrieves an entity’s navigation properties—1:N, N:1, and N:N relationships—and optionally filters by a related entity to map Dataverse connections.

Instructions

Get navigation properties (relationships) for an entity, including 1:N, N:1, and N:N relationships.

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": {
      "entity_name": "<entity_name>"
    },
    "name": "get_entity_navigation_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
entity_nameYesLogical name of the entity
environment_profileNoOptional named environment profile for this call; omit to use the configured default.
related_entity_nameNoOptional: Filter by a specific related entity

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.2
    • addedInput schema / properties / environment_profile
      Added value: +{
      +  "description": "Optional named environment profile for this call; omit to use the configured default.",
      +  "pattern": "^[A-Za-z][A-Za-z0-9_]{0,31}$",
      +  "type": "string"
      +}
  2. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It implies a read operation but never explicitly states read-only behavior, permissions, side effects, or whether system relationships are included; beyond naming relationship types, it adds little behavioral context.

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 definition is a single front-loaded sentence with no filler or redundant wording. It states the action and the relationship types immediately.

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 read-only metadata tool with no annotations and no output schema, the description names the returned concept and relationship cardinalities but does not describe the return shape, pagination, or usage context. The input schema is fully documented, so the remaining gap is moderate rather than severe.

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%, and the schema fully documents entity_name, optional environment_profile, and optional related_entity_name. The description adds no parameter meaning beyond saying the lookup is 'for an entity,' so the baseline of 3 applies when the schema does the heavy lifting.

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 uses a specific verb ('Get') and resource ('navigation properties (relationships) for an entity'), and explicitly names the relationship cardinalities (1:N, N:1, N:N). It does not distinguish this tool from siblings such as get_model_relationship or get_entity_metadata_summary.

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 guidance about when to use this tool instead of related siblings like get_model_relationship, get_entity_metadata_summary, or get_detailed_field_metadata. It also omits prerequisites, exclusions, or context that would help an agent choose among similar metadata retrieval tools.

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