Skip to main content
Glama
mwhesse

Dataverse MCP Server

by mwhesse

List Dataverse Publishers

list_dataverse_publishers

Retrieve publishers from Dataverse to discover available publishers, find custom publishers for solution creation, or view publisher configurations with customization prefixes.

Instructions

Retrieves a list of publishers in the Dataverse environment with filtering options. Use this to discover available publishers, find custom publishers for solution creation, or get an overview of publisher configurations including customization prefixes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customOnlyNoWhether to list only custom publishers
topNoMaximum number of publishers to return

Implementation Reference

  • The main handler function for the 'list_dataverse_publishers' tool. It builds OData query parameters based on input (customOnly filter, top limit), fetches publishers from the Dataverse API, maps the response to a clean format, and returns a markdown-formatted list or error response.
    async (params) => {
      try {
        let queryParams: Record<string, any> = {
          $select: "friendlyname,uniquename,customizationprefix,customizationoptionvalueprefix,description,isreadonly"
        };
    
        let filters: string[] = [];
        
        if (params.customOnly) {
          filters.push("isreadonly eq false");
        }
    
        if (filters.length > 0) {
          queryParams.$filter = filters.join(" and ");
        }
    
        if (params.top) {
          queryParams.$top = params.top;
        }
    
        const result = await client.get('publishers', queryParams);
    
        const publisherList = result.value.map((publisher: any) => ({
          friendlyName: publisher.friendlyname,
          uniqueName: publisher.uniquename,
          customizationPrefix: publisher.customizationprefix,
          customizationOptionValuePrefix: publisher.customizationoptionvalueprefix,
          description: publisher.description,
          isReadOnly: publisher.isreadonly
        }));
    
        return {
          content: [
            {
              type: "text",
              text: `Found ${publisherList.length} publishers:\n\n${JSON.stringify(publisherList, null, 2)}`
            }
          ]
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text: `Error listing publishers: ${error instanceof Error ? error.message : 'Unknown error'}`
            }
          ],
          isError: true
        };
      }
    }
  • Zod input schema defining parameters for the tool: customOnly (boolean, defaults to true for custom publishers only), top (optional number for pagination).
    inputSchema: {
      customOnly: z.boolean().default(true).describe("Whether to list only custom publishers"),
      top: z.number().optional().describe("Maximum number of publishers to return")
    }
  • The server.registerTool call within listPublishersTool function that registers the 'list_dataverse_publishers' tool, including its title, description, input schema, and handler reference.
    server.registerTool(
      "list_dataverse_publishers",
      {
        title: "List Dataverse Publishers",
        description: "Retrieves a list of publishers in the Dataverse environment with filtering options. Use this to discover available publishers, find custom publishers for solution creation, or get an overview of publisher configurations including customization prefixes.",
        inputSchema: {
          customOnly: z.boolean().default(true).describe("Whether to list only custom publishers"),
          top: z.number().optional().describe("Maximum number of publishers to return")
        }
      },
      async (params) => {
        try {
          let queryParams: Record<string, any> = {
            $select: "friendlyname,uniquename,customizationprefix,customizationoptionvalueprefix,description,isreadonly"
          };
    
          let filters: string[] = [];
          
          if (params.customOnly) {
            filters.push("isreadonly eq false");
          }
    
          if (filters.length > 0) {
            queryParams.$filter = filters.join(" and ");
          }
    
          if (params.top) {
            queryParams.$top = params.top;
          }
    
          const result = await client.get('publishers', queryParams);
    
          const publisherList = result.value.map((publisher: any) => ({
            friendlyName: publisher.friendlyname,
            uniqueName: publisher.uniquename,
            customizationPrefix: publisher.customizationprefix,
            customizationOptionValuePrefix: publisher.customizationoptionvalueprefix,
            description: publisher.description,
            isReadOnly: publisher.isreadonly
          }));
    
          return {
            content: [
              {
                type: "text",
                text: `Found ${publisherList.length} publishers:\n\n${JSON.stringify(publisherList, null, 2)}`
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error listing publishers: ${error instanceof Error ? error.message : 'Unknown error'}`
              }
            ],
            isError: true
          };
        }
      }
    );
  • src/index.ts:172-172 (registration)
    Invocation of listPublishersTool in the main index.ts file, which triggers the registration of the tool on the MCP server instance.
    listPublishersTool(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 filtering options and some use cases, it doesn't describe important behavioral aspects like whether this is a read-only operation, potential rate limits, authentication requirements, pagination behavior, or what happens when no publishers match filters. The description adds some context but leaves significant gaps for a tool with mutation siblings.

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 appropriately sized with two sentences that efficiently cover purpose and usage. The first sentence states the core functionality, and the second provides use case examples. There's minimal redundancy, though the phrase 'with filtering options' could be slightly more specific given the schema already documents this.

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 no annotations and no output schema, the description provides adequate basic information but lacks completeness for a tool in a context with many mutation siblings. It doesn't clarify whether this is a safe read operation versus potentially having side effects, nor does it describe return format or error conditions. For a list operation with filtering, more behavioral context would be helpful.

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 100%, so the schema already documents both parameters completely. The description mentions 'filtering options' which aligns with the 'customOnly' parameter, and 'discover available publishers' relates to the list retrieval, but adds no specific syntax, format, or semantic details beyond what the schema provides. Baseline 3 is appropriate when schema does the heavy lifting.

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 tool retrieves a list of publishers in the Dataverse environment with filtering options. It specifies the resource (publishers) and verb (retrieves/list), but doesn't explicitly differentiate from potential sibling tools like 'get_dataverse_publisher' which appears to fetch a single publisher rather than a list.

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

Usage Guidelines3/5

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

The description provides implied usage context with phrases like 'Use this to discover available publishers, find custom publishers for solution creation, or get an overview of publisher configurations.' However, it doesn't explicitly state when to use this tool versus alternatives like 'get_dataverse_publisher' or provide exclusion criteria.

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