Skip to main content
Glama
mwhesse

Dataverse MCP Server

by mwhesse

Create Dataverse Publisher

create_dataverse_publisher

Create a publisher identity in Dataverse to establish customization prefixes for schema names and enable solution creation for custom components.

Instructions

Creates a new publisher in Dataverse. Publishers are required for creating solutions and provide customization prefixes for schema names. Use this to establish a publisher identity before creating solutions and custom components.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customizationOptionValuePrefixYesOption value prefix (e.g., 72700)
customizationPrefixYesCustomization prefix for schema names (e.g., 'sample')
descriptionNoDescription of the publisher
friendlyNameYesFriendly name for the publisher
uniqueNameYesUnique name for the publisher (e.g., 'examplepublisher')

Implementation Reference

  • The handler function that constructs the publisher definition object and uses DataverseClient.post to create the publisher in Dataverse, returning formatted success or error response.
    async (params) => {
      try {
        const publisherDefinition = {
          friendlyname: params.friendlyName,
          uniquename: params.uniqueName,
          description: params.description || `Publisher for ${params.friendlyName}`,
          customizationprefix: params.customizationPrefix,
          customizationoptionvalueprefix: params.customizationOptionValuePrefix
        };
    
        const result = await client.post('publishers', publisherDefinition);
    
        return {
          content: [
            {
              type: "text",
              text: `Successfully created publisher '${params.friendlyName}' with prefix '${params.customizationPrefix}'.\n\nResponse: ${JSON.stringify(result, null, 2)}`
            }
          ]
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text: `Error creating publisher: ${error instanceof Error ? error.message : 'Unknown error'}`
            }
          ],
          isError: true
        };
      }
    }
  • Zod input schema defining the parameters required to create a Dataverse publisher.
    inputSchema: {
      friendlyName: z.string().describe("Friendly name for the publisher"),
      uniqueName: z.string().describe("Unique name for the publisher (e.g., 'examplepublisher')"),
      description: z.string().optional().describe("Description of the publisher"),
      customizationPrefix: z.string().describe("Customization prefix for schema names (e.g., 'sample')"),
      customizationOptionValuePrefix: z.number().describe("Option value prefix (e.g., 72700)")
    }
  • The server.registerTool call that defines and registers the 'create_dataverse_publisher' tool including its name, title, description, input schema, and handler function.
    server.registerTool(
      "create_dataverse_publisher",
      {
        title: "Create Dataverse Publisher",
        description: "Creates a new publisher in Dataverse. Publishers are required for creating solutions and provide customization prefixes for schema names. Use this to establish a publisher identity before creating solutions and custom components.",
        inputSchema: {
          friendlyName: z.string().describe("Friendly name for the publisher"),
          uniqueName: z.string().describe("Unique name for the publisher (e.g., 'examplepublisher')"),
          description: z.string().optional().describe("Description of the publisher"),
          customizationPrefix: z.string().describe("Customization prefix for schema names (e.g., 'sample')"),
          customizationOptionValuePrefix: z.number().describe("Option value prefix (e.g., 72700)")
        }
      },
      async (params) => {
        try {
          const publisherDefinition = {
            friendlyname: params.friendlyName,
            uniquename: params.uniqueName,
            description: params.description || `Publisher for ${params.friendlyName}`,
            customizationprefix: params.customizationPrefix,
            customizationoptionvalueprefix: params.customizationOptionValuePrefix
          };
    
          const result = await client.post('publishers', publisherDefinition);
    
          return {
            content: [
              {
                type: "text",
                text: `Successfully created publisher '${params.friendlyName}' with prefix '${params.customizationPrefix}'.\n\nResponse: ${JSON.stringify(result, null, 2)}`
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error creating publisher: ${error instanceof Error ? error.message : 'Unknown error'}`
              }
            ],
            isError: true
          };
        }
      }
    );
  • src/index.ts:167-167 (registration)
    Top-level call to createPublisherTool which performs the actual registration of the tool on the MCP server.
    createPublisherTool(server, dataverseClient);
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. While it mentions that publishers are 'required for creating solutions,' it doesn't disclose important behavioral traits like whether this is a write operation (implied but not stated), what permissions are needed, whether the creation is permanent or reversible, or what happens on failure. For a creation tool with zero annotation coverage, this leaves significant gaps.

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 perfectly concise with two sentences that each earn their place. The first sentence states the core purpose, and the second provides essential usage context. There's zero wasted language, and the information is front-loaded appropriately.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that this is a creation tool with no annotations and no output schema, the description should do more to compensate. While it explains the purpose and basic usage context, it doesn't address behavioral aspects like error conditions, response format, or system impacts. The 100% schema coverage helps, but for a write operation, the description lacks completeness.

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 schema description coverage is 100%, so the schema already documents all 5 parameters thoroughly. The description adds some context about why publishers matter ('provide customization prefixes for schema names'), which relates to the 'customizationPrefix' parameter, but doesn't provide additional parameter-specific semantics beyond what the schema descriptions already offer.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('creates a new publisher'), resource ('in Dataverse'), and purpose ('required for creating solutions and provide customization prefixes for schema names'). It distinguishes this tool from sibling tools like 'get_dataverse_publisher' or 'list_dataverse_publishers' by focusing on creation rather than retrieval.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use this tool ('to establish a publisher identity before creating solutions and custom components'), which helps guide the agent. However, it doesn't explicitly state when NOT to use it or mention specific alternatives like 'update_dataverse_publisher' (though that tool doesn't exist in the sibling list).

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/mwhesse/mcp-dataverse'

If you have feedback or need assistance with the MCP directory API, please join our Discord server