Skip to main content
Glama
rafteles2016

MCP Dynamics CRM Server

by rafteles2016

dynamics_update_column

Modify column properties in Microsoft Dynamics CRM, including display name, description, required level, and maximum length for existing attributes.

Instructions

Atualiza propriedades de uma coluna existente

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entityLogicalNameYesNome lógico da entidade
attributeLogicalNameYesNome lógico do atributo
displayNameNo
descriptionNo
requiredLevelNo
maxLengthNo

Implementation Reference

  • The handler function for dynamics_update_column that processes parameters and executes a patch request to the Dynamics API.
    server.tool(
      "dynamics_update_column",
      "Atualiza propriedades de uma coluna existente",
      UpdateColumnSchema.shape,
      async (params: z.infer<typeof UpdateColumnSchema>) => {
        const updateData: Record<string, unknown> = {};
        if (params.displayName) {
          updateData.DisplayName = {
            "@odata.type": "Microsoft.Dynamics.CRM.Label",
            LocalizedLabels: [{ "@odata.type": "Microsoft.Dynamics.CRM.LocalizedLabel", Label: params.displayName, LanguageCode: 1046 }],
          };
        }
        if (params.description) {
          updateData.Description = {
            "@odata.type": "Microsoft.Dynamics.CRM.Label",
            LocalizedLabels: [{ "@odata.type": "Microsoft.Dynamics.CRM.LocalizedLabel", Label: params.description, LanguageCode: 1046 }],
          };
        }
        if (params.requiredLevel) {
          updateData.RequiredLevel = { Value: params.requiredLevel };
        }
        if (params.maxLength !== undefined) {
          updateData.MaxLength = params.maxLength;
        }
    
        await client.patch(
          `EntityDefinitions(LogicalName='${params.entityLogicalName}')/Attributes(LogicalName='${params.attributeLogicalName}')`,
          updateData
        );
    
        return {
          content: [
            {
              type: "text" as const,
              text: `Coluna ${params.attributeLogicalName} atualizada com sucesso!`,
            },
  • The Zod schema definition (UpdateColumnSchema) for the input validation of the dynamics_update_column tool.
    export const UpdateColumnSchema = z.object({
      entityLogicalName: z.string().describe("Nome lógico da entidade"),
      attributeLogicalName: z.string().describe("Nome lógico do atributo"),
      displayName: z.string().optional(),
      description: z.string().optional(),
      requiredLevel: z.enum(["None", "SystemRequired", "ApplicationRequired"]).optional(),
      maxLength: z.number().optional(),
    });
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Atualiza' implies a mutation operation, the description doesn't address critical behaviors: whether this requires specific permissions, if changes are reversible, what happens to existing data in the column, error conditions, or response format. For a mutation tool with zero annotation coverage, this leaves significant gaps.

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 zero wasted words. It's appropriately front-loaded with the core action and target, making it easy to parse quickly. No unnecessary elaboration or redundancy is present.

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 tool's complexity (mutation operation with 6 parameters, no annotations, and no output schema), the description is inadequate. It doesn't explain what properties can be updated, how the update affects the system, what the response contains, or error handling. For a tool that modifies database schema elements, more contextual information is needed.

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 only 33% (2 out of 6 parameters have descriptions), and the description provides no additional parameter information. It doesn't explain what 'entityLogicalName' or 'attributeLogicalName' refer to, nor does it clarify the purpose of 'displayName', 'description', 'requiredLevel', or 'maxLength'. The description fails to compensate for the low schema coverage.

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

Purpose3/5

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

The description states the action ('Atualiza' - Updates) and the target ('propriedades de uma coluna existente' - properties of an existing column), which provides a basic understanding of the tool's function. However, it doesn't differentiate this tool from sibling tools like 'dynamics_update_form' or 'dynamics_update_web_resource' beyond the resource type, and the purpose remains somewhat vague about what specific properties can be updated.

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. There's no mention of prerequisites (e.g., needing an existing column), when not to use it, or how it differs from related tools like 'dynamics_create_column' or 'dynamics_delete_column'. The agent must infer usage from the name and schema alone.

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/rafteles2016/mcpDynamics'

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