Skip to main content
Glama
rafteles2016

MCP Dynamics CRM Server

by rafteles2016

dynamics_delete_column

Remove a column from a Dynamics CRM table to modify database structure or clean up unused fields. Specify entity and attribute names to delete the column.

Instructions

Remove uma coluna de uma tabela

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entityLogicalNameYesNome lógico da entidade
attributeLogicalNameYesNome lógico do atributo

Implementation Reference

  • Handler for dynamics_delete_column which deletes a column from a Dynamics table using the Dataverse client.
    // 10. Delete Column
    server.tool(
      "dynamics_delete_column",
      "Remove uma coluna de uma tabela",
      DeleteColumnSchema.shape,
      async (params: z.infer<typeof DeleteColumnSchema>) => {
        await client.delete(
          `EntityDefinitions(LogicalName='${params.entityLogicalName}')/Attributes(LogicalName='${params.attributeLogicalName}')`
        );
    
        return {
          content: [
            {
              type: "text" as const,
              text: `Coluna ${params.attributeLogicalName} removida de ${params.entityLogicalName} com sucesso!`,
            },
          ],
        };
      }
    );
  • Input schema validation for dynamics_delete_column.
    export const DeleteColumnSchema = z.object({
      entityLogicalName: z.string().describe("Nome lógico da entidade"),
      attributeLogicalName: z.string().describe("Nome lógico do atributo"),
    });
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. It states 'Remove' implying a destructive mutation, but lacks details on permissions needed, whether the action is reversible, potential side effects, or error conditions. This is inadequate for a tool that deletes data without structured safety hints.

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, direct sentence in Portuguese with no wasted words. It's front-loaded with the core action and target, making it efficient and easy to parse, though it could benefit from additional context.

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?

For a destructive tool with no annotations and no output schema, the description is insufficient. It doesn't cover behavioral aspects like safety, permissions, or return values, leaving critical gaps for an agent to understand the tool's full impact and usage.

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%, with both parameters ('entityLogicalName' and 'attributeLogicalName') clearly described in the schema. The description doesn't add any meaning beyond the schema, such as examples or constraints, so it meets the baseline for high schema coverage without extra value.

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 'Remove uma coluna de uma tabela' clearly states the action (remove) and target (a column from a table) in Portuguese. It's specific about what the tool does, though it doesn't explicitly differentiate from sibling tools like 'dynamics_update_column' or 'dynamics_list_columns' beyond the verb 'remove'.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, consequences, or sibling tools like 'dynamics_update_column' for modifications or 'dynamics_list_columns' for checking existing columns, leaving the agent without context for selection.

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