Skip to main content
Glama

Set project group

set_project_group
Destructive

Make a group of projects, rename one or delete one. 'group' names it (its name, any case, or its id); a name the company has no group by makes one. 'rename' gives an existing group a new name; 'delete': true removes it — its projects stay, in no group, and the people put in it by hand leave it. The company's administrator only; every change is in the company's journal.

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": {
      "group": "<group>"
    },
    "name": "set_project_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupYesThe group's name, e.g. 'Client A', or its id.
deleteNoTrue to delete the group.
renameNoA new name for an existing group.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true so the delete risk is known, but the description goes further by spelling out the blast radius: projects survive in no group and hand-added people are removed. It also discloses the admin-only permission requirement and that changes are journaled in the company's journal — information annotations cannot express.

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?

Two dense sentences, front-loaded with the action summary before parameter semantics. Every clause carries information — modes, lookup behavior, and deletion consequences — with no filler.

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?

For a 3-parameter, annotation-covered destructive mutation, the description covers permissions, side effects, and audit trail well. Minor gaps remain: behavior when renaming a group that does not exist, and no indication of what the call returns (no output schema exists).

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?

Schema coverage is 100%, so baseline is 3, and the description earns the extra point by clarifying that 'group' accepts a name in any case or an id, and by disclosing create-on-miss upsert semantics that the schema's plain 'The group's name ... or its id' does not state.

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 opens with a concrete verb set and resource: 'Make a group of projects, rename one or delete one,' which tells an agent this is the group lifecycle tool (create/rename/delete). It does not explicitly name a sibling like set_project_group_person to contrast membership operations, but the three modes are unambiguous.

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?

Usage is conveyed through parameter semantics: naming a non-existent group creates it, 'rename' requires an existing group, and 'delete': true removes it. This gives clear context for selecting each mode, though there is no explicit 'when not to use this' or pointer to alternatives for adding people or moving projects.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources