Skip to main content
Glama
rafteles2016

MCP Dynamics CRM Server

by rafteles2016

dynamics_export_solution

Export Dynamics CRM solutions as Base64 ZIP files for backup, migration, or deployment purposes, with configurable settings for customization and system data.

Instructions

Exporta uma solução do Dynamics CRM (retorna Base64 do ZIP)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
solutionUniqueNameYesNome único da solução
managedNoExportar como managed
exportAutoNumberingSettingsNo
exportCalendarSettingsNo
exportCustomizationSettingsNo
exportEmailTrackingSettingsNo
exportGeneralSettingsNo
exportIsvConfigNo
exportMarketingSettingsNo
exportOutlookSynchronizationSettingsNo
exportRelationshipRolesNo
exportSalesNo

Implementation Reference

  • The dynamics_export_solution tool handler is defined and registered here. It uses ExportSolutionSchema to validate inputs, performs an "ExportSolution" action via the client, and returns a text response.
    server.tool(
      "dynamics_export_solution",
      "Exporta uma solução do Dynamics CRM (retorna Base64 do ZIP)",
      ExportSolutionSchema.shape,
      async (params: z.infer<typeof ExportSolutionSchema>) => {
        const result = await client.executeAction<{ ExportSolutionFile: string }>("ExportSolution", {
          SolutionName: params.solutionUniqueName,
          Managed: params.managed,
          ExportAutoNumberingSettings: params.exportAutoNumberingSettings,
          ExportCalendarSettings: params.exportCalendarSettings,
          ExportCustomizationSettings: params.exportCustomizationSettings,
          ExportEmailTrackingSettings: params.exportEmailTrackingSettings,
          ExportGeneralSettings: params.exportGeneralSettings,
          ExportIsvConfig: params.exportIsvConfig,
          ExportMarketingSettings: params.exportMarketingSettings,
          ExportOutlookSynchronizationSettings: params.exportOutlookSynchronizationSettings,
          ExportRelationshipRoles: params.exportRelationshipRoles,
          ExportSales: params.exportSales,
        });
    
        const sizeKb = Math.round((result.ExportSolutionFile?.length || 0) * 0.75 / 1024);
    
        return {
          content: [
            {
              type: "text" as const,
              text: `Solução ${params.solutionUniqueName} exportada com sucesso!\nTipo: ${params.managed ? "Managed" : "Unmanaged"}\nTamanho: ~${sizeKb} KB\n\n(O conteúdo Base64 do ZIP está disponível para download)`,
            },
          ],
        };
      }
    );
  • Schema definition for the inputs required by the dynamics_export_solution tool.
    export const ExportSolutionSchema = z.object({
      solutionUniqueName: z.string().describe("Nome único da solução"),
      managed: z.boolean().default(false).describe("Exportar como managed"),
      exportAutoNumberingSettings: z.boolean().default(false),
      exportCalendarSettings: z.boolean().default(false),
      exportCustomizationSettings: z.boolean().default(false),
      exportEmailTrackingSettings: z.boolean().default(false),
      exportGeneralSettings: z.boolean().default(false),
      exportIsvConfig: z.boolean().default(false),
      exportMarketingSettings: z.boolean().default(false),
      exportOutlookSynchronizationSettings: z.boolean().default(false),
      exportRelationshipRoles: z.boolean().default(false),
      exportSales: z.boolean().default(false),
    });
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 mentions the return format (Base64 ZIP) but lacks critical behavioral details: it doesn't specify if this is a read-only operation, what permissions are required, whether it affects system state, potential side effects (e.g., locking), or error handling. For a tool with 12 parameters and no annotations, this is a significant gap in transparency.

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 that front-loads the core purpose ('Exporta uma solução do Dynamics CRM') and adds essential output detail ('retorna Base64 do ZIP'). There is zero waste—every word contributes to understanding the tool's function without redundancy or fluff.

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 (12 parameters, no output schema, no annotations), the description is incomplete. It covers the basic purpose and output format but misses behavioral context, parameter explanations, and usage guidelines. For a tool that exports solutions—a potentially sensitive operation—more detail on permissions, effects, and error cases is needed to be fully helpful to an AI agent.

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 low at 17%, with only 2 of 12 parameters having descriptions. The tool description adds no parameter semantics beyond what's in the schema—it doesn't explain what 'solutionUniqueName' refers to, clarify the boolean flags (e.g., what 'managed' means or the impact of export settings), or provide examples. With poor schema coverage, the description fails to compensate, leaving most parameters undocumented.

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 ('Exporta uma solução') and resource ('do Dynamics CRM'), specifying it returns a Base64 ZIP. It distinguishes from siblings like 'dynamics_import_solution' and 'dynamics_list_solutions' by focusing on export functionality. However, it doesn't explicitly differentiate from other export-related tools if they existed, though none are present in the sibling list.

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 an existing solution), compare it to similar tools like 'dynamics_clone_solution' or 'dynamics_get_solution_components', or specify scenarios where export is appropriate (e.g., for backup or migration). Usage is implied but not explicitly stated.

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