Skip to main content
Glama
mwhesse

Dataverse MCP Server

by mwhesse

Get Dataverse Publisher

get_dataverse_publisher

Retrieve detailed publisher information including customization prefix, option value prefix, and configuration settings to understand Dataverse customization properties.

Instructions

Retrieves detailed information about a specific publisher including its customization prefix, option value prefix, and configuration. Use this to inspect publisher properties and understand customization settings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uniqueNameYesUnique name of the publisher to retrieve

Implementation Reference

  • Handler function that executes the tool: queries Dataverse publishers by uniqueName and returns formatted information or error.
    async (params) => {
      try {
        const result = await client.get(
          `publishers?$filter=uniquename eq '${params.uniqueName}'`
        );
    
        if (!result.value || result.value.length === 0) {
          throw new Error(`Publisher with unique name '${params.uniqueName}' not found`);
        }
    
        return {
          content: [
            {
              type: "text",
              text: `Publisher information for '${params.uniqueName}':\n\n${JSON.stringify(result.value[0], null, 2)}`
            }
          ]
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text: `Error retrieving publisher: ${error instanceof Error ? error.message : 'Unknown error'}`
            }
          ],
          isError: true
        };
      }
    }
  • Input schema validating the uniqueName parameter.
    inputSchema: {
      uniqueName: z.string().describe("Unique name of the publisher to retrieve")
    }
  • Registration of the get_dataverse_publisher tool within the getPublisherTool function.
    server.registerTool(
      "get_dataverse_publisher",
      {
        title: "Get Dataverse Publisher",
        description: "Retrieves detailed information about a specific publisher including its customization prefix, option value prefix, and configuration. Use this to inspect publisher properties and understand customization settings.",
        inputSchema: {
          uniqueName: z.string().describe("Unique name of the publisher to retrieve")
        }
      },
      async (params) => {
        try {
          const result = await client.get(
            `publishers?$filter=uniquename eq '${params.uniqueName}'`
          );
    
          if (!result.value || result.value.length === 0) {
            throw new Error(`Publisher with unique name '${params.uniqueName}' not found`);
          }
    
          return {
            content: [
              {
                type: "text",
                text: `Publisher information for '${params.uniqueName}':\n\n${JSON.stringify(result.value[0], null, 2)}`
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error retrieving publisher: ${error instanceof Error ? error.message : 'Unknown error'}`
              }
            ],
            isError: true
          };
        }
      }
    );
  • src/index.ts:170-170 (registration)
    Invocation of getPublisherTool which registers the tool with the MCP server.
    getPublisherTool(server, dataverseClient);
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 of behavioral disclosure. It describes the tool as a retrieval operation, which implies it's read-only and non-destructive, but doesn't explicitly state this or mention any constraints like authentication requirements, rate limits, or error conditions. The description adds some context about what information is retrieved but lacks comprehensive behavioral details.

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 concise and well-structured in two sentences: the first states the purpose, and the second provides usage guidance. It's front-loaded with the core functionality and avoids unnecessary details. However, it could be slightly more efficient by combining ideas, but overall it's clear and wastes no words.

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 the tool's low complexity (single parameter, no output schema, no annotations), the description is moderately complete. It covers the purpose and usage but lacks behavioral transparency details that would be crucial without annotations. For a simple retrieval tool, it's adequate but could benefit from more explicit safety and constraint information to fully guide the agent.

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 input schema has 100% description coverage, with the single parameter 'uniqueName' well-documented in the schema. The description doesn't add any additional parameter semantics beyond what's in the schema, such as format examples or validation rules. Given the high schema coverage, the baseline score of 3 is appropriate as the 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's purpose with the verb 'retrieves' and specifies the resource as 'detailed information about a specific publisher'. It mentions specific properties like 'customization prefix, option value prefix, and configuration', which helps distinguish it from generic retrieval tools. However, it doesn't explicitly differentiate from sibling tools like 'list_dataverse_publishers' beyond implying this is for a single publisher versus 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 guidance by stating 'Use this to inspect publisher properties and understand customization settings', which suggests when this tool is appropriate. However, it doesn't explicitly mention when not to use it or name alternatives like 'list_dataverse_publishers' for browsing multiple publishers, leaving some ambiguity for the agent.

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