Skip to main content
Glama
srikanth-paladugula

Dynamics 365 MCP Server

update-account

Modify existing account records in Dynamics 365 by providing account ID and updated data fields.

Instructions

Update an existing account in Dynamics 365

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountIdYes
accountDataYes

Implementation Reference

  • The handler function registered for the 'update-account' MCP tool. It extracts parameters, invokes the Dynamics365 updateAccount method, formats the response as text content, and handles errors appropriately.
      async (params) => {
        try {
          const { accountId, accountData } = params;
          const response = await d365.updateAccount(accountId, accountData);
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(response, null, 2),
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error: ${
                  error instanceof Error ? error.message : "Unknown error"
                }, please check your input and try again.`,
              },
            ],
            isError: true,
          };
        }
      }
    );
  • Zod schema defining the input parameters for the 'update-account' tool: accountId as string and accountData as object.
    {
      accountId: z.string(),
      accountData: z.object({}),
    },
  • src/tools.ts:136-170 (registration)
    Registration of the 'update-account' tool using server.tool(), including name, description, schema, and handler function.
    // Register the "update-account" tool
    server.tool(
      "update-account",
      "Update an existing account in Dynamics 365",
      {
        accountId: z.string(),
        accountData: z.object({}),
      },
      async (params) => {
        try {
          const { accountId, accountData } = params;
          const response = await d365.updateAccount(accountId, accountData);
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(response, null, 2),
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error: ${
                  error instanceof Error ? error.message : "Unknown error"
                }, please check your input and try again.`,
              },
            ],
            isError: true,
          };
        }
      }
    );
  • Helper method in Dynamics365 class that performs the actual account update by making a PATCH request to the Dynamics 365 Web API endpoint.
    public async updateAccount(
      accountId: string,
      accountData: any
    ): Promise<any> {
      if (!accountId) {
        throw new Error("Account ID is required to update an account.");
      }
    
      if (!accountData) {
        throw new Error("Account data is required to update an account.");
      }
    
      const endpoint = `api/data/v9.2/accounts(${accountId})`;
      return this.makeApiRequest(endpoint, "PATCH", accountData);
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Update' implies a mutation, but fails to mention critical details like required permissions, whether changes are reversible, error handling, or rate limits. This leaves significant gaps in understanding the tool's behavior.

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 description is a single, efficient sentence with no wasted words. It is front-loaded with the core action and resource, making it easy to parse quickly, which is ideal for conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a mutation tool with no annotations, 0% schema coverage, and no output schema, the description is incomplete. It lacks details on parameters, behavioral traits, return values, and usage context, making it inadequate for safe and effective tool invocation.

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

Parameters1/5

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

Schema description coverage is 0%, meaning the schema provides no parameter details. The description adds no information about the parameters 'accountId' (e.g., format, source) or 'accountData' (e.g., allowed fields, structure), failing to compensate for the lack of schema documentation.

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 clearly states the verb ('Update') and resource ('an existing account in Dynamics 365'), making the tool's purpose understandable. However, it doesn't differentiate from sibling tools like 'create-account' or 'fetch-accounts' beyond the basic verb distinction, which prevents a perfect score.

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 'create-account' for new accounts or 'fetch-accounts' for reading. It lacks context on prerequisites, such as needing an existing account ID, or exclusions, leaving the agent without clear usage direction.

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/srikanth-paladugula/mcp-dyamics365-server'

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