Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

get_environment_capabilities

Read-only

Inspects the configured CRM environment by reading WhoAmI, version, and table metadata, separating confirmed metadata evidence from untested permissions and SDK support.

Instructions

Read WhoAmI, RetrieveVersion and table definitions to inspect the configured CRM environment. Reports metadata evidence separately from untested permissions and SDK support; does not change the connection or select another API version.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_environment_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.7/5.0
Behavior4/5

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

readOnlyHint=true already declares the safety profile, and the description adds genuinely new behavioral context: it distinguishes reported metadata evidence from permissions and SDK support that remain untested, which warns the agent not to treat the output as a verification result. That nuance is not derivable from annotations or schema, though it says nothing about output shape or failure modes.

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 sentences, front-loaded with the concrete read operation and followed by the scoping caveat; no filler. The second sentence is somewhat abstractly worded ('metadata evidence separately from untested permissions') and could be tighter.

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?

For a zero-required-parameter read tool with no output schema, the description adequately names what is retrieved (WhoAmI, RetrieveVersion, table definitions) and what the results do and do not represent. Nothing critical is missing, though a note on output granularity would have made it fully self-contained.

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?

With one optional parameter at 100% schema description coverage, the schema already explains environment_profile as an optional named profile that defaults when omitted. The description adds no further meaning about profile selection, 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?

Names a specific verb-and-resource set (read WhoAmI, RetrieveVersion and table definitions) plus the object it targets (the configured CRM environment), which is concrete enough to distinguish it from metadata siblings like get_entity_metadata_summary or list_all_entity_definitions. It stops short of naming any sibling explicitly, so it remains a 4 rather than a 5.

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 negative scoping ('does not change the connection or select another API version') tells the agent what this tool will not do, which implicitly frames it as a pre-flight inspection call. However, there is no explicit instruction on when to prefer it over get_current_user_context, get_diagnostic_settings, or check_model_configuration, so the when-to-use guidance is only implied.

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