GitFlic MCP Server

gitflic_release_edit

DestructiveIdempotent

Update release metadata such as title, description, tag, and pre-release status for a GitFlic project release identified by its UUID.

Instructions

Edit release metadata.

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>",
      "uuid": "<uuid>"
    },
    "name": "gitflic_release_edit"
  }
}

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.
`tag`	No
`uuid`	Yes
`title`	No
`project`	Yes
`preRelease`	No
`description`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.1Nov 13, 2026

TDQS

C2/5.0

Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is carried by structured data. The description adds nothing beyond that — it never says what "edit" destroys (e.g. whether an omitted field is cleared, whether the tag can be reassigned) or what permissions are needed, which matters for a destructive, open-world mutation.

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

Conciseness2/5

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

Four words with zero waste, but also zero payload — this is under-specification rather than conciseness. There is no front-loaded scope statement for the agent to anchor on.

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

Completeness1/5

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

A 7-parameter, 2-required destructive mutation with 14% schema coverage and no output schema needs the description to explain field semantics, partial-update behavior, and side effects. At four words it is wholly inadequate to the tool's complexity.

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

Parameters1/5

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

Schema description coverage is 14%: only the `raw` escape hatch is documented, leaving uuid, project, tag, title, description, and preRelease entirely unannotated. The description supplies zero parameter meaning and does not even hint that partial updates are supported or what omitting a field means.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Edit release metadata" names a verb and a resource, so the broad intent is legible. It gives no scope detail (which fields, which release) and does nothing to distinguish it from gitflic_release_create, gitflic_release_delete, or gitflic_release_get.

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 release_create or release_delete, no prerequisites (does the release need to exist? are you required to be the author?), and no mention of partial vs full update semantics. The agent must infer everything from the name.

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

Deploy Server