GitFlic MCP Server

gitflic_project_member_invite

Destructive

Invite a user to a GitFlic project and assign a role to control their access.

Instructions

Invite a user to a project with a role.

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>",
      "userAlias": "<userAlias>",
      "role": "<role>"
    },
    "name": "gitflic_project_member_invite"
  }
}

Input Schema

Name	Required	Description
`raw`	No	Return the full, un-slimmed GitFlic response for THIS call (no token compression). Use when the default slim view dropped a field you need.
`role`	Yes
`project`	Yes
`userAlias`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.1Nov 13, 2026

TDQS

C2.7/5.0

Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the description should explain the consequences: that this grants persistent access, what happens on re-invite of an existing member, and whether the caller needs admin rights. It adds none of that; "invite a user with a role" restates the tool name without disclosing any of the risky behavior the annotations flag.

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?

A single front-loaded sentence with no filler or repetition. Its problem is under-specification, not verbosity, so it scores well on structure while leaving substance missing.

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

Completeness2/5

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

This is a destructive, non-idempotent mutation with no output schema and three undocumented required parameters. For that complexity the description should at minimum cover permission prerequisites and the meaning of the role levels; as written it is too thin to call safely.

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

Parameters2/5

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

Schema description coverage is only 25% – among project, userAlias and role only the auxiliary `raw` flag is documented. The description says "with a role" but never explains what GUEST/REPORTER/DEVELOPER/MAINTAINER/OWNER grant, nor what form project (id vs path) or userAlias (login vs email) take. It fails to compensate for the coverage gap.

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 ("Invite") and resource ("a user to a project") plus the role modifier, which clearly separates it from gitflic_project_member_list or gitflic_project_create. It stops short of naming a sibling it is not, so it does not reach 5.

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?

There is no when-to-use guidance, no prerequisite (e.g. must the user exist, must the inviter be an owner), and no mention of checking existing membership first. The agent is left to infer the entire calling context from the name alone.

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

Deploy Server