Skip to main content
Glama
mwhesse

Dataverse MCP Server

by mwhesse

Delete Dataverse Team

delete_dataverse_team

Remove a team from Dataverse permanently. This action cannot be undone and requires verifying the team has no assigned records or security roles before deletion.

Instructions

Permanently deletes a team from Dataverse. WARNING: This action cannot be undone and will fail if the team owns records or has assigned security roles. Ensure the team is not in use before deletion.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
teamIdYesID of the team to delete

Implementation Reference

  • The asynchronous handler function that executes the core logic of deleting the specified Dataverse team using the DataverseClient's delete method.
    async (params) => {
      try {
        await client.delete(`teams(${params.teamId})`);
    
        return {
          content: [
            {
              type: "text",
              text: `Successfully deleted team.`
            }
          ]
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text: `Error deleting team: ${error instanceof Error ? error.message : 'Unknown error'}`
            }
          ],
          isError: true
        };
      }
    }
  • The input schema defining the required 'teamId' parameter using Zod validation.
      teamId: z.string().describe("ID of the team to delete")
    }
  • The server.registerTool call that registers the 'delete_dataverse_team' tool, including its schema and inline handler.
      "delete_dataverse_team",
      {
        title: "Delete Dataverse Team",
        description: "Permanently deletes a team from Dataverse. WARNING: This action cannot be undone and will fail if the team owns records or has assigned security roles. Ensure the team is not in use before deletion.",
        inputSchema: {
          teamId: z.string().describe("ID of the team to delete")
        }
      },
      async (params) => {
        try {
          await client.delete(`teams(${params.teamId})`);
    
          return {
            content: [
              {
                type: "text",
                text: `Successfully deleted team.`
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error deleting team: ${error instanceof Error ? error.message : 'Unknown error'}`
              }
            ],
            isError: true
          };
        }
      }
    );
  • src/index.ts:202-202 (registration)
    The invocation of deleteTeamTool in the main index file, which triggers the tool registration on the MCP server.
    deleteTeamTool(server, dataverseClient);
Behavior5/5

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

With no annotations provided, the description carries the full burden and excels by disclosing critical behavioral traits: it is destructive ('permanently deletes', 'cannot be undone'), has specific failure conditions ('will fail if the team owns records or has assigned security roles'), and requires pre-checks ('ensure the team is not in use'). This goes beyond the basic input schema to inform the agent about risks and constraints.

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 appropriately sized and front-loaded: the first sentence states the core purpose, followed by warnings and prerequisites. Every sentence earns its place by adding critical information without redundancy, making it efficient and easy to parse.

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

Completeness4/5

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

Given the tool's complexity (destructive deletion with conditions), no annotations, and no output schema, the description is largely complete: it covers purpose, behavioral risks, and usage context. However, it does not specify what happens on success (e.g., confirmation message) or error details beyond failure conditions, leaving some gaps in full contextual understanding.

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 (the 'teamId' parameter is well-documented in the schema), so the baseline is 3. The description does not add any additional parameter-specific information beyond what the schema provides, such as format examples or validation rules, but it doesn't need to since the schema is comprehensive.

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 ('permanently deletes') and resource ('a team from Dataverse'), distinguishing it from sibling tools like 'delete_dataverse_businessunit' or 'delete_dataverse_table' which target different resources. It avoids tautology by not just restating the name/title.

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 by warning about prerequisites ('will fail if the team owns records or has assigned security roles') and advising to 'ensure the team is not in use before deletion.' However, it does not explicitly mention when not to use it or name specific alternatives among siblings (e.g., 'update_dataverse_team' for modifications instead of deletion).

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