GitFlic MCP Server

gitflic_release_get

Read-only

Retrieves a single GitFlic release by project and UUID, with options to narrow returned fields or get the full raw response.

Instructions

Get one release by uuid.

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_get"
  }
}

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.
`uuid`	Yes
`fields`	No	Return only these top-level fields (plus id keys), narrowing the response further.
`project`	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 readOnlyHint=true and destructiveHint=false, so the safety profile is covered, but the description adds nothing beyond the title: no note on error behavior for an unknown uuid, no mention of the slimmed response the 'raw' parameter implies, no cross-project access notes. It is consistent with the annotations, just not additive.

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?

One short, front-loaded sentence with zero filler, but it is under-specified rather than efficient — the brevity costs useful routing and parameter information.

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?

A read-only single-item fetch is a simple tool, and there is no output schema to explain, so the minimal description is not disastrous. However, with two undocumented required parameters and a 'raw'/'fields' slimming mechanism hinted at only in the schema, the definition leaves an agent to guess how to form a valid call.

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 coverage is only 50%: 'raw' and 'fields' are documented in the schema, while the required 'project' and 'uuid' have no schema descriptions. The description clarifies only that uuid identifies the release and says nothing about which project namespace is expected, so it does not compensate for the 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?

States a specific verb and resource ('Get one release') and the lookup key ('by uuid'), which is enough to distinguish it from create/edit/delete/list siblings. It does not explicitly name a sibling, so it stops short of a 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?

No when-to-use guidance at all: nothing says to use this instead of gitflic_release_list or gitflic_release_latest when the uuid is unknown or when the newest release is wanted. The agent must infer selection criteria from tool names alone.

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

Deploy Server