Skip to main content
Glama
rafteles2016

MCP Dynamics CRM Server

by rafteles2016

dynamics_create_publisher

Create a new solution publisher in Dynamics CRM to organize customizations with unique names, prefixes, and descriptions for deployment.

Instructions

Cria um novo publicador de soluções

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uniqueNameYesNome único do publicador
friendlyNameYesNome amigável
customizationPrefixYesPrefixo de customização (ex: new)
customizationOptionValuePrefixYesPrefixo de valor de opção (ex: 10000)
descriptionNo

Implementation Reference

  • Tool handler for 'dynamics_create_publisher' in 'src/tools/solutions/index.ts'.
    server.tool(
      "dynamics_create_publisher",
      "Cria um novo publicador de soluções",
      CreatePublisherSchema.shape,
      async (params: z.infer<typeof CreatePublisherSchema>) => {
        const result = await client.create("publishers", {
          uniquename: params.uniqueName,
          friendlyname: params.friendlyName,
          customizationprefix: params.customizationPrefix,
          customizationoptionvalueprefix: params.customizationOptionValuePrefix,
          description: params.description || "",
        });
    
        return {
          content: [
            {
              type: "text" as const,
              text: `Publicador criado!\nID: ${result.entityId}\nNome: ${params.uniqueName}\nPrefixo: ${params.customizationPrefix}`,
            },
          ],
        };
      }
  • Schema definition for 'dynamics_create_publisher' input validation.
    export const CreatePublisherSchema = z.object({
      uniqueName: z.string().describe("Nome único do publicador"),
      friendlyName: z.string().describe("Nome amigável"),
      customizationPrefix: z.string().describe("Prefixo de customização (ex: new)"),
      customizationOptionValuePrefix: z.number().describe("Prefixo de valor de opção (ex: 10000)"),
      description: z.string().optional(),
    });
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. It states this is a creation operation but doesn't mention permissions required, whether this is a write operation, what happens on success/failure, or any side effects. The description is minimal and doesn't provide the behavioral context needed for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that states the core purpose without unnecessary words. However, it's arguably too concise given the complexity of creating a publisher in Dynamics, which likely has important behavioral considerations not mentioned.

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 mutation tool with no annotations and no output schema, the description is inadequate. It doesn't explain what a 'solution publisher' is in the Dynamics context, what happens after creation, whether there are dependencies or prerequisites, or what the tool returns. The context signals show this is a 5-parameter tool with 4 required parameters, yet the description provides minimal guidance.

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 description adds no additional parameter information beyond what's in the schema. It doesn't explain the purpose of a 'solution publisher' or how the parameters relate to the publisher's function in the Dynamics ecosystem.

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' - creates) and resource ('um novo publicador de soluções' - a new solution publisher), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'dynamics_list_publishers' or explain how this differs from other creation tools in the set.

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 are multiple sibling tools for creating various Dynamics resources (columns, relationships, solutions, tables, views, web resources), but no indication of when to create a publisher specifically versus other resources.

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