Skip to main content
Glama

Move project to group

move_project_to_group
Destructive

Put a project in a group of projects — out of the one it was in — or, with no 'group', in none. Whose names the project offers when somebody picks a person changes at once. The company's administrator only; a project's own owner cannot. 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": {
      "projectKey": "<projectKey>"
    },
    "name": "move_project_to_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupNoThe group's name or id; leave out for no group.
projectKeyYesProject key, e.g. 'ACME'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only flag destructiveHint=true and readOnlyHint=false; the description adds genuinely new behavior: the operation is admin-only, it changes which names the project offers in a person picker immediately, and it is recorded in the company journal. Those are exactly the side-effect and permission details an agent needs before a destructive write. It stops short of stating whether the move is reversible or what the response contains.

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

Conciseness3/5

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

Three sentences, no filler, and the move semantics are front-loaded. But the middle sentence — 'Whose names the project offers when somebody picks a person changes at once' — is garbled to the point that an agent may misparse the actual side effect, which costs more than the brevity saves.

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 two-parameter mutation with no output schema, the description covers the important ground: permission requirement, side effect, and audit trail, on top of annotations that already flag destructiveness. Only the reversibility question and the near-duplicate sibling distinction are left open.

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% and the schema already documents both parameters, including 'leave out for no group'. The description's recital of the no-group case merely restates the schema default rather than adding format or syntax detail. Baseline 3 is appropriate.

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?

States a specific verb and resource: 'Put a project in a group of projects — out of the one it was in.' The scope (exactly one group at a time, or none) is unambiguous. It does not differentiate from the sibling 'set_project_group', which reads as a near-duplicate name, leaving the agent to guess between them.

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

Usage Guidelines3/5

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

The description gives a real precondition — 'The company's administrator only; a project's own owner cannot' — which is useful before calling. However, it never says when to prefer this over the similarly named sibling 'set_project_group', nor does it state any exclusions or failure conditions beyond the permission gate.

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