keyshade-mcp

Official

by keyshade-xyz

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

create_workspace_role

Creates a workspace role with specified name, authorities, and optional project environment permissions.

Instructions

Creates a new workspace role

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": {
      "workspaceSlug": "<workspaceSlug>",
      "name": "<name>"
    },
    "name": "create_workspace_role"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`colorCode`	No
`authorities`	No
`description`	No
`workspaceSlug`	Yes
`projectEnvironments`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 30, 2026

TDQS

C2.3/5.0

Behavior1/5

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

With no annotations and no additional behavioral disclosure, the description says nothing about side effects, required permissions, rate limits, or invariants. For a creation tool, important traits like whether duplicates are allowed or changes are idempotent are omitted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise (one sentence) but at the cost of completeness. It repeats the tool name and adds no additional value. For a tool with 6 parameters, more structure or key information is needed.

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

Completeness1/5

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

Given the tool's complexity (6 parameters, no output schema, no annotations), the description is highly incomplete. It fails to explain return values, required permissions, error conditions, or any contextual information about workspace roles.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description adds no meaning to any of the 6 parameters. It does not hint at required fields, format expectations, or relationships between parameters (e.g., 'projectEnvironments' structure).

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 'Creates a new workspace role' clearly states the action (create) and the resource (workspace role). It distinguishes the tool from siblings like 'update_workspace_role' and 'delete_workspace_role' by implying the create operation.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool, prerequisites, or when to prefer alternatives. The agent receives no context about typical use cases or exclusions, such as not to use if role already exists.

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