Skip to main content
Glama

Set project group person

set_project_group_person
Destructive

Put somebody of the company in a group of projects by hand — a person on none of its projects who should be offered in them — or take them out ('inGroup': false). Taking out removes only the hand-made place: somebody on one of the group's projects stays in it by being there. The company's administrator only. 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>",
      "who": "<who>"
    },
    "name": "set_project_group_person"
  }
}

Input Schema

NameRequiredDescriptionDefault
whoYesThe person's username or e-mail.
groupYesThe group's name or id.
inGroupNoTrue to put them in (the default), false to take them out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Beyond annotations, it discloses the key scope-of-destruction fact: removal only deletes the hand-made place, and anyone on one of the group's projects stays in it by being there. It adds an authorization requirement and an audit note ('In the company's journal'). This meaningfully qualifies the destructiveHint=true annotation rather than contradicting it.

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 action and its inverse are front-loaded, and every sentence carries substance (scope, removal semantics, permissions, audit). The phrasing is somewhat convoluted ('somebody of the company in a group of projects by hand') and could be tighter, but there is 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 mutation with annotations and no output schema, the description covers authorization, audit trail, and side-effect scope. Minor gaps remain, such as idempotency when the person is already manually in the group and what confirmation or result to expect.

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 the baseline is 3, but the description adds real interpretation of 'inGroup': false — what it removes and what it leaves intact. The 'who' and 'group' parameters get no extra clarification beyond the schema's username/e-mail and name/id notes.

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 names a specific verb and resource: manually placing or removing a person in a project group ('Put somebody ... in a group of projects by hand ... or take them out'). It also implicitly distinguishes itself from other group tools by emphasizing the hand-made, per-person membership rather than group configuration, though it never names a sibling explicitly.

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?

It clearly states the target case — a person on none of the group's projects who should still be offered in them — and distinguishes the removal path via 'inGroup': false. It also states a hard prerequisite ('The company's administrator only'). No named alternative tool is given for other membership scenarios, which keeps it from a 5.

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