Skip to main content
Glama
mwhesse

Dataverse MCP Server

by mwhesse

Update Dataverse Team

update_dataverse_team

Modify team settings like name, description, administrator, or configuration properties for existing Dataverse teams without affecting team membership.

Instructions

Updates the properties and configuration of an existing team. Use this to modify team settings like name, description, administrator, or other team properties without changing team membership.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
administratorIdNoNew administrator user ID
azureActiveDirectoryObjectIdNoAzure AD Object ID for the team
delegatedAuthorizationIdNoDelegated authorization context for the team
descriptionNoNew description of the team
emailAddressNoEmail address for the team
membershipTypeNoMembership type: 0=Members and guests, 1=Members, 2=Owners, 3=Guests
nameNoNew name of the team
queueIdNoDefault queue ID for the team
teamIdYesID of the team to update
teamTemplateIdNoTeam template ID to associate with the team
teamTypeNoTeam type: 0=Owner, 1=Access, 2=Security Group, 3=Office Group
transactionCurrencyIdNoCurrency ID associated with the team
yomiNameNoPronunciation of the team name in phonetic characters

Implementation Reference

  • Executes the tool logic by constructing update data from params and patching the Dataverse teams endpoint via the client.
    async (params) => {
      try {
        const updateData: any = {};
    
        if (params.name !== undefined) updateData.name = params.name;
        if (params.description !== undefined) updateData.description = params.description;
        if (params.teamType !== undefined) updateData.teamtype = parseInt(params.teamType);
        if (params.membershipType !== undefined) updateData.membershiptype = parseInt(params.membershipType);
        if (params.emailAddress !== undefined) updateData.emailaddress = params.emailAddress;
        if (params.yomiName !== undefined) updateData.yominame = params.yomiName;
        if (params.azureActiveDirectoryObjectId !== undefined) updateData.azureactivedirectoryobjectid = params.azureActiveDirectoryObjectId;
    
        // Set optional relationships
        if (params.administratorId !== undefined) {
          updateData['administratorid@odata.bind'] = `/systemusers(${params.administratorId})`;
        }
        if (params.queueId !== undefined) {
          updateData['queueid@odata.bind'] = params.queueId ? `/queues(${params.queueId})` : null;
        }
        if (params.teamTemplateId !== undefined) {
          updateData['teamtemplateid@odata.bind'] = params.teamTemplateId ? `/teamtemplates(${params.teamTemplateId})` : null;
        }
        if (params.delegatedAuthorizationId !== undefined) {
          updateData['delegatedauthorizationid@odata.bind'] = params.delegatedAuthorizationId ? `/delegatedauthorizations(${params.delegatedAuthorizationId})` : null;
        }
        if (params.transactionCurrencyId !== undefined) {
          updateData['transactioncurrencyid@odata.bind'] = params.transactionCurrencyId ? `/transactioncurrencies(${params.transactionCurrencyId})` : null;
        }
    
        await client.patch(`teams(${params.teamId})`, updateData);
    
        return {
          content: [
            {
              type: "text",
              text: `Successfully updated team.`
            }
          ]
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text: `Error updating team: ${error instanceof Error ? error.message : 'Unknown error'}`
            }
          ],
          isError: true
        };
      }
    }
  • Zod input schema defining parameters for updating a Dataverse team, including optional fields for various team properties.
    inputSchema: {
      teamId: z.string().describe("ID of the team to update"),
      name: z.string().max(160).optional().describe("New name of the team"),
      description: z.string().max(2000).optional().describe("New description of the team"),
      teamType: z.enum(['0', '1', '2', '3']).optional().describe("Team type: 0=Owner, 1=Access, 2=Security Group, 3=Office Group"),
      membershipType: z.enum(['0', '1', '2', '3']).optional().describe("Membership type: 0=Members and guests, 1=Members, 2=Owners, 3=Guests"),
      emailAddress: z.string().max(100).optional().describe("Email address for the team"),
      yomiName: z.string().max(160).optional().describe("Pronunciation of the team name in phonetic characters"),
      azureActiveDirectoryObjectId: z.string().optional().describe("Azure AD Object ID for the team"),
      administratorId: z.string().optional().describe("New administrator user ID"),
      queueId: z.string().optional().describe("Default queue ID for the team"),
      teamTemplateId: z.string().optional().describe("Team template ID to associate with the team"),
      delegatedAuthorizationId: z.string().optional().describe("Delegated authorization context for the team"),
      transactionCurrencyId: z.string().optional().describe("Currency ID associated with the team")
    }
  • Registers the 'update_dataverse_team' tool with the MCP server using server.registerTool, providing title, description, input schema, and handler function.
    export function updateTeamTool(server: McpServer, client: DataverseClient) {
      server.registerTool(
        "update_dataverse_team",
        {
          title: "Update Dataverse Team",
          description: "Updates the properties and configuration of an existing team. Use this to modify team settings like name, description, administrator, or other team properties without changing team membership.",
          inputSchema: {
            teamId: z.string().describe("ID of the team to update"),
            name: z.string().max(160).optional().describe("New name of the team"),
            description: z.string().max(2000).optional().describe("New description of the team"),
            teamType: z.enum(['0', '1', '2', '3']).optional().describe("Team type: 0=Owner, 1=Access, 2=Security Group, 3=Office Group"),
            membershipType: z.enum(['0', '1', '2', '3']).optional().describe("Membership type: 0=Members and guests, 1=Members, 2=Owners, 3=Guests"),
            emailAddress: z.string().max(100).optional().describe("Email address for the team"),
            yomiName: z.string().max(160).optional().describe("Pronunciation of the team name in phonetic characters"),
            azureActiveDirectoryObjectId: z.string().optional().describe("Azure AD Object ID for the team"),
            administratorId: z.string().optional().describe("New administrator user ID"),
            queueId: z.string().optional().describe("Default queue ID for the team"),
            teamTemplateId: z.string().optional().describe("Team template ID to associate with the team"),
            delegatedAuthorizationId: z.string().optional().describe("Delegated authorization context for the team"),
            transactionCurrencyId: z.string().optional().describe("Currency ID associated with the team")
          }
        },
        async (params) => {
          try {
            const updateData: any = {};
    
            if (params.name !== undefined) updateData.name = params.name;
            if (params.description !== undefined) updateData.description = params.description;
            if (params.teamType !== undefined) updateData.teamtype = parseInt(params.teamType);
            if (params.membershipType !== undefined) updateData.membershiptype = parseInt(params.membershipType);
            if (params.emailAddress !== undefined) updateData.emailaddress = params.emailAddress;
            if (params.yomiName !== undefined) updateData.yominame = params.yomiName;
            if (params.azureActiveDirectoryObjectId !== undefined) updateData.azureactivedirectoryobjectid = params.azureActiveDirectoryObjectId;
    
            // Set optional relationships
            if (params.administratorId !== undefined) {
              updateData['administratorid@odata.bind'] = `/systemusers(${params.administratorId})`;
            }
            if (params.queueId !== undefined) {
              updateData['queueid@odata.bind'] = params.queueId ? `/queues(${params.queueId})` : null;
            }
            if (params.teamTemplateId !== undefined) {
              updateData['teamtemplateid@odata.bind'] = params.teamTemplateId ? `/teamtemplates(${params.teamTemplateId})` : null;
            }
            if (params.delegatedAuthorizationId !== undefined) {
              updateData['delegatedauthorizationid@odata.bind'] = params.delegatedAuthorizationId ? `/delegatedauthorizations(${params.delegatedAuthorizationId})` : null;
            }
            if (params.transactionCurrencyId !== undefined) {
              updateData['transactioncurrencyid@odata.bind'] = params.transactionCurrencyId ? `/transactioncurrencies(${params.transactionCurrencyId})` : null;
            }
    
            await client.patch(`teams(${params.teamId})`, updateData);
    
            return {
              content: [
                {
                  type: "text",
                  text: `Successfully updated team.`
                }
              ]
            };
          } catch (error) {
            return {
              content: [
                {
                  type: "text",
                  text: `Error updating team: ${error instanceof Error ? error.message : 'Unknown error'}`
                }
              ],
              isError: true
            };
          }
        }
      );
    }
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 indicates this is a mutation tool ('Updates'), but doesn't describe what happens on success/failure, whether changes are reversible, authentication requirements, rate limits, or response format. For a tool with 13 parameters and no output schema, this leaves significant behavioral 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 important clarification about what this tool does NOT do (change membership). No wasted words or redundant information.

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 complex mutation tool with 13 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what happens after the update, error conditions, permission requirements, or how it differs from other update tools in the sibling list. The agent would need to guess about important behavioral aspects.

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 all 13 parameters thoroughly with descriptions, enums, and constraints. The description adds minimal value by mentioning examples like 'name, description, administrator' which are already in the schema, but doesn't provide additional context about parameter interactions or usage patterns beyond what's in the structured schema.

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 verb ('Updates') and resource ('properties and configuration of an existing team'), with specific examples of settings that can be modified (name, description, administrator). It distinguishes from membership changes by explicitly stating 'without changing team membership', which helps differentiate from sibling tools like add_members_to_team and remove_members_from_team, though it doesn't explicitly name those alternatives.

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 some implied guidance by stating 'without changing team membership', suggesting this tool is for property updates rather than membership management. However, it doesn't explicitly state when to use this versus other update tools (like update_dataverse_businessunit or update_dataverse_role) or mention prerequisites like required permissions or team existence.

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