Skip to main content
Glama
Sign In
plane-ce-mcp

plane-ce-mcp

by Bl4nk44
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

update_workspace_features

Idempotent

Enable or disable workspace features including project grouping, initiatives, teams, customers, wiki, and program increments.

Instructions

Update features of the current workspace.

Args: project_grouping: Enable/disable project grouping feature initiatives: Enable/disable initiatives feature teams: Enable/disable teams feature customers: Enable/disable customers feature wiki: Enable/disable wiki feature pi: Enable/disable PI (Program Increment) feature

Returns: Updated WorkspaceFeature object

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "update_workspace_features"
  }
}

Input Schema

NameRequiredDescriptionDefault
piNo
wikiNo
teamsNo
customersNo
initiativesNo
project_groupingNo

Output Schema

NameRequiredDescriptionDefault
piYes
wikiYes
teamsYes
customersYes
initiativesYes
project_groupingYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description adds only that it 'updates features', which is consistent but does not provide additional behavioral context such as scope of changes (e.g., affects all projects) or potential side effects. With annotations covering the safety profile, a 3 is appropriate.

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 concise and well-structured, with a one-line summary, a list of parameters with explanations, and a return type statement. Every sentence serves a purpose and there is no redundant information.

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 that there is an output schema and all parameters are optional, the description adequately explains the tool's purpose and parameters. However, it lacks usage context or guidance on when to use this tool versus siblings, which is a gap for completeness. Still, the tool is simple and the main details are covered.

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

Parameters4/5

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

The schema has 0% description coverage, so the description carries the full burden. Each parameter is explained with 'Enable/disable [feature] feature', which adds clear meaning beyond the raw boolean/null type. However, it lacks details like default behavior or interaction between parameters, which could be useful. This is a solid addition but not exhaustive.

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 'Update features of the current workspace', specifying the verb and resource. It distinguishes from sibling tools like 'update_project_features' by explicitly mentioning workspace. The argument list further clarifies the exact features affected.

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?

The description provides no guidance on when to use this tool versus alternatives such as 'update_project_features' or other feature-related tools. There is no mention of prerequisites, typical use cases, or exclusions, leaving the agent to infer context.

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