Skip to main content
Glama
rafteles2016

MCP Dynamics CRM Server

by rafteles2016

dynamics_publish_customizations

Publish all customizations or customizations for a specific entity in Microsoft Dynamics CRM to apply changes and make them available in the system.

Instructions

Publica todas as customizações ou customizações de uma entidade específica

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entityLogicalNameNoNome da entidade (vazio = publicar tudo)

Implementation Reference

  • Handler for the dynamics_publish_customizations tool, which invokes either PublishXml (for a specific entity) or PublishAllXml on the Dataverse client.
    // 12. Publish Customizations
    server.tool(
      "dynamics_publish_customizations",
      "Publica todas as customizações ou customizações de uma entidade específica",
      z.object({
        entityLogicalName: z.string().optional().describe("Nome da entidade (vazio = publicar tudo)"),
      }).shape,
      async (params: { entityLogicalName?: string }) => {
        if (params.entityLogicalName) {
          await client.executeAction("PublishXml", {
            ParameterXml: `<importexportxml><entities><entity>${params.entityLogicalName}</entity></entities></importexportxml>`,
          });
        } else {
          await client.executeAction("PublishAllXml", {});
        }
    
        return {
          content: [
            {
              type: "text" as const,
              text: params.entityLogicalName
                ? `Customizações de ${params.entityLogicalName} publicadas com sucesso!`
                : "Todas as customizações foram publicadas com sucesso!",
            },
          ],
        };
      }
    );
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 the action ('publish') which implies a write operation, but doesn't clarify critical aspects like whether this is destructive (e.g., overwrites existing customizations), requires specific permissions, has side effects (e.g., system downtime), or rate limits. The description lacks behavioral context beyond the basic action.

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 in Portuguese that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy to understand at a glance.

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 publish operation in Dynamics (likely involving system changes), no annotations, and no output schema, the description is incomplete. It doesn't explain what 'publish' entails (e.g., deployment to production, validation steps), potential impacts, error handling, or return values. For a tool that could affect system behavior, more context is needed.

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?

The input schema has 100% description coverage, with the parameter 'entityLogicalName' documented as 'Nome da entidade (vazio = publicar tudo)' (Entity name (empty = publish all)). The description adds minimal value beyond this, only restating that it can publish all customizations or those of a specific entity. With high schema coverage, the baseline score of 3 is appropriate.

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 action ('Publica' = Publish) and the target ('customizações' = customizations), specifying it can publish all customizations or those of a specific entity. It distinguishes itself from other publish-related tools like 'dynamics_publish_web_resources' by focusing on customizations rather than web resources. However, it could be more specific about what 'customizations' entail in the Dynamics context.

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. It doesn't mention prerequisites (e.g., needing customizations to exist), exclusions, or compare it to sibling tools like 'dynamics_publish_web_resources' or 'dynamics_update_form' for similar publishing/updating tasks. Usage is implied but not explicitly defined.

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