Skip to main content
Glama
Sign In
warp-mcp

warp-mcp

by Ringer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Duplicate a role

team_duplicate_role

Create a customer-owned role by copying scopes from any source role, including system roles, so you can customize permissions safely. Requires team:write scope.

Instructions

Create a new customer-owned role copying the source role's scope set (the source may be a system role). Useful for customizing a system role: duplicate it, then adjust scopes with team_update_role. The caller must hold every copied scope. Requires the team:write scope.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "customer_id": "<customer_id>",
      "role_id": "<role_id>",
      "name": "<name>",
      "display_name": "<display_name>"
    },
    "name": "team_duplicate_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesMachine name for the new role (unique within the customer), e.g. 'support_admin_custom'
role_idYesSource role UUID to copy scopes from (find it via team_list_roles)
customer_idYesYour customer UUID (shown in the WARP portal under Settings)
descriptionNoOptional free-text description of the new role
display_nameYesHuman-readable name for the new role

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.1/5.0
Behavior4/5

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

Annotations indicate non-read-only, non-idempotent, non-destructive. The description adds that it creates a new role, requires team:write scope, and that the caller must hold every copied scope. It does not discuss reversibility or side effects, but given the simple creation nature, it is adequately transparent.

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 two sentences plus a requirement sentence. It is front-loaded with the primary action. It could be slightly more concise by integrating the requirement into the main sentence, but overall it is efficient and clear.

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 no output schema and moderate complexity, the description covers the core operation, prerequisite, and suggested workflow. It does not mention return values, but for a creation tool this is acceptable. It is reasonably complete for an agent to use effectively.

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 coverage is 100%, so baseline is 3. The description adds sourcing hints like 'find it via team_list_roles' for role_id and 'shown in the WARP portal under Settings' for customer_id, but does not clarify the distinction between name and display_name beyond schema descriptions.

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 it creates a new role by copying scopes from a source, specifying it can copy from system roles. This distinguishes it from sibling tools like team_create_role (which creates from scratch) and team_update_role (which modifies an existing role).

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?

Explicitly says 'Useful for customizing a system role: duplicate it, then adjust scopes with team_update_role.' This provides a clear use case and alternative. It also mentions a prerequisite: 'The caller must hold every copied scope.' However, it lacks explicit when-not-to-use guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools