@illodev/taiga-mcp

taiga_memberships_create

Invite a user to a Taiga project by creating a membership with specified role. Provide project ID, role ID, and username to grant access.

Instructions

Create a membership (invite user to project).

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": {
      "project": "<project>",
      "role": "<role>",
      "username": "<username>"
    },
    "name": "taiga_memberships_create"
  }
}

Input Schema

Name	Required	Description
`role`	Yes	Role ID
`project`	Yes	Project ID
`username`	Yes	Username or email to invite

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

B3.3/5.0

Behavior2/5

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

There are no annotations, so the description must disclose behavioral aspects. It only says 'Create a membership' without mentioning side effects like email invitations, permission requirements, or error conditions when the user already exists or the role is invalid.

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 a single concise sentence that is front-loaded with the action. No unnecessary words or repetition, earning a high score for conciseness.

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

Completeness3/5

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

For a simple create operation with three self-documenting parameters, the description is minimally viable. However, with no annotations or output schema, it lacks details on implications (e.g., whether an invitation email is sent, if membership is immediate) and does not fully cover the operation's context.

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?

The schema provides descriptions for all three parameters (project, role, username), so coverage is 100%. The description's parenthetical 'invite user to project' adds minor context to the parameters but does not significantly enhance understanding beyond the schema.

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 'Create a membership (invite user to project)' clearly states the action and the specific resource. It distinguishes this tool from other membership operations like list, get, update, delete, and bulk_create by focusing on the singular creation of a membership.

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 versus alternatives such as taiga_memberships_bulk_create or how to handle existing users. The description merely states what it does without any prerequisites, use-case context, or exclusions.

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

Deploy Server