Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

get_entity_metadata_summary

Retrieve a concise summary of entity metadata covering primary keys, name fields, and key business attributes, excluding redundant fields. Use it to quickly understand entity structure.

Instructions

Get a summary of entity metadata including primary key, name field, and business-relevant attributes. System-redundant fields are excluded.

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": {
      "logical_name": "<logical_name>"
    },
    "name": "get_entity_metadata_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
logical_nameYesLogical name of the entity (e.g., account, contact)
environment_profileNoOptional named environment profile for this call; omit to use the configured default.

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

A3.5/5.0
Behavior3/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 does disclose one real behavior beyond the schema: system-redundant fields are filtered out of the result. It does not state that the call is read-only (only implied by "Get"), nor what happens when an unknown or unresolvable logical_name is passed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with the main purpose front-loaded and the exclusion rule second. No filler, though the second sentence could have been merged into the first without loss.

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?

The tool is a simple two-parameter read with no output schema, and the description does describe the shape of the return (primary key, name field, business-relevant attributes). Together with a fully documented schema, that is enough for an agent to call it correctly, with only minor gaps around failure behavior.

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%, so both parameters (logical_name and environment_profile) are already fully documented with examples and defaults. The description adds no further meaning about parameter semantics, so the baseline 3 applies.

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 states a specific verb+resource ("Get a summary of entity metadata") and enumerates the contents (primary key, name field, business-relevant attributes). It implicitly contrasts with detail-oriented siblings like get_detailed_field_metadata or get_model_definition through the word "summary", but it never names an alternative explicitly.

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?

Usage is only implied: an agent can infer this is the lightweight metadata call to use before drilling into detailed field metadata, but there is no explicit when-to-use or when-not-to-use statement and no named alternative among the many metadata siblings. The "system-redundant fields are excluded" note hints at a lightweight role without spelling it out.

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