Skip to main content
Glama
rafteles2016

MCP Dynamics CRM Server

by rafteles2016

dynamics_create_solution

Create new solutions in Dynamics CRM by defining unique names, display names, publisher IDs, and version details to organize customizations and extensions.

Instructions

Cria uma nova solução no Dynamics CRM

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uniqueNameYesNome único da solução (sem espaços)
displayNameYesNome de exibição
publisherIdYesID do publicador
versionNoVersão (ex: 1.0.0.0)1.0.0.0
descriptionNo

Implementation Reference

  • The handler function for the "dynamics_create_solution" tool.
    server.tool(
      "dynamics_create_solution",
      "Cria uma nova solução no Dynamics CRM",
      CreateSolutionSchema.shape,
      async (params: z.infer<typeof CreateSolutionSchema>) => {
        const data = {
          uniquename: params.uniqueName,
          friendlyname: params.displayName,
          version: params.version,
          description: params.description || "",
          "publisherid@odata.bind": `/publishers(${params.publisherId})`,
        };
    
        const result = await client.create("solutions", data);
    
        return {
          content: [
            {
              type: "text" as const,
              text: `Solução criada com sucesso!\nID: ${result.entityId}\nNome: ${params.uniqueName}\nVersão: ${params.version}`,
            },
          ],
        };
      }
    );
  • Zod schema defining the input parameters for the "dynamics_create_solution" tool.
    export const CreateSolutionSchema = z.object({
      uniqueName: z.string().describe("Nome único da solução (sem espaços)"),
      displayName: z.string().describe("Nome de exibição"),
      publisherId: z.string().describe("ID do publicador"),
      version: z.string().default("1.0.0.0").describe("Versão (ex: 1.0.0.0)"),
      description: z.string().optional(),
    });
  • Registration of the "dynamics_create_solution" tool within the registerSolutionTools function.
    export function registerSolutionTools(
      server: { tool: Function },
      client: DataverseClient
    ) {
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Cria uma nova solução' implies a write/mutation operation, it doesn't disclose permission requirements, whether this is an idempotent operation, what happens on failure, or any rate limits. The description provides minimal 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 for a basic creation tool and front-loads the essential information.

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 creation/mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what constitutes a successful creation, what gets returned (if anything), error conditions, or how this tool relates to the many sibling solution management tools. The context demands more guidance for proper agent 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 80% (4 of 5 parameters have descriptions), so the baseline is 3. The tool description adds no parameter-specific information beyond what's already in the schema descriptions, which adequately document uniqueName, displayName, publisherId, and version parameters.

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 ('Cria uma nova solução') and target resource ('no Dynamics CRM'), providing a specific verb+resource combination. However, it doesn't differentiate this from sibling tools like 'dynamics_clone_solution' or 'dynamics_import_solution' which also create solutions through different mechanisms.

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. With multiple solution-related tools available (create, clone, import, delete, list solutions), there's no indication of prerequisites, appropriate contexts, or when other tools might be more suitable.

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