Skip to main content
Glama
mafzaal

Dynamics 365 Finance & Operations MCP Server

by mafzaal

d365fo_update_profile

Update a Dynamics 365 Finance & Operations environment profile with full configuration options, automatically invalidating cached client connections to apply new settings.

Instructions

Update an existing D365FO environment profile with full configuration options.

Automatically invalidates all cached client connections to ensure they pick up the new profile settings on next use.

Args: name: Profile name baseUrl: D365FO base URL description: Profile description verifySsl: Whether to verify SSL certificates timeout: Request timeout in seconds useLabelCache: Whether to enable label caching labelCacheExpiryMinutes: Label cache expiry in minutes useCacheFirst: Whether to use cache-first behavior language: Default language code cacheDir: Custom cache directory path outputFormat: Default output format for CLI operations credentialSource: Credential source configuration. Set to null to use Azure Default Credentials. Can be: - Environment variables: {"sourceType": "environment", "clientIdVar": "MY_CLIENT_ID", "clientSecretVar": "MY_CLIENT_SECRET", "tenantIdVar": "MY_TENANT_ID"} - Azure Key Vault: {"sourceType": "keyvault", "vaultUrl": "https://vault.vault.azure.net/", "clientIdSecretName": "D365FO_CLIENT_ID", "clientSecretSecretName": "D365FO_CLIENT_SECRET", "tenantIdSecretName": "D365FO_TENANT_ID"}

Returns: Dictionary with update result including number of clients invalidated

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
baseUrlNo
timeoutNo
cacheDirNo
languageNo
verifySslNo
descriptionNo
outputFormatNo
useCacheFirstNo
useLabelCacheNo
credentialSourceNo
labelCacheExpiryMinutesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

The description discloses that it 'automatically invalidates all cached client connections,' a behavioral trait beyond the name. No annotations are provided, so the description carries full burden; it adds meaningful context about side effects and return value.

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

Conciseness3/5

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

The description includes a parameter list and return type, but the parameter list largely duplicates schema information. It is moderately concise but could be shortened by omitting parameter names already present in 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 tool with 12 parameters and a nested object, the description covers purpose, a key behavioral detail (cache invalidation), and return structure. However, it lacks explanations for most parameters, leaving the agent without essential context for many inputs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%. The description lists parameter names but only explains the 'credentialSource' parameter in detail. The other 11 parameters have no additional semantics beyond what the schema provides (type, default).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Update an existing D365FO environment profile with full configuration options,' clearly indicating the verb (update) and resource (profile). This distinguishes it from siblings like create_profile and delete_profile.

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 provides no guidance on when to use this tool versus alternatives like d365fo_create_profile or d365fo_clone_profile. It does not mention prerequisites, limitations, or when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mafzaal/d365fo-client'

If you have feedback or need assistance with the MCP directory API, please join our Discord server