GitFlic MCP Server

gitflic_issue_create

DestructiveIdempotent

Create a new issue in a GitFlic project by providing the project, title, and description; optionally set status or return the full raw response.

Instructions

Create a new issue.

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>",
      "title": "<title>",
      "description": "<description>"
    },
    "name": "gitflic_issue_create"
  }
}

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.
`title`	Yes
`status`	No	default: OPEN
`project`	Yes
`description`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.1Nov 13, 2026

TDQS

C2.6/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond them — no note on what the issue creation touches, whether it notifies watchers, or what fields come back. With annotations carrying the burden, the description still could have added useful context and does not.

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?

The single sentence is front-loaded and free of waste, but this is brevity by omission rather than tight writing; there is simply nothing to structure.

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?

For a five-parameter mutation with only 40% schema coverage and no output schema, the description should at minimum explain the required inputs and what a successful create returns. It leaves the agent dependent on the schema and annotations alone.

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 40%: project, title and description are required but undocumented, and only raw and status carry descriptions in the schema. The description does not compensate at all — it names no parameters, no formats, and no default for status.

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?

"Create a new issue" states a specific verb (create) and resource (issue), which is unambiguous about the operation. It does not distinguish this from siblings such as gitflic_issue_edit or gitflic_issue_comment, so it falls short of the 5-level bar.

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 guidance on when to use this versus gitflic_issue_edit, gitflic_issue_reopen, or gitflic_issue_comment, and no prerequisites (project access, auth) are mentioned. The agent must infer everything from the tool name.

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

Deploy Server