GitFlic MCP Server

gitflic_release_list

Read-only

List and filter GitFlic project releases by tag, title, stability, and sort order, so you can find relevant release entries without fetching full data.

Instructions

List releases.

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

Input Schema

Name	Required	Description
`q`	No	Free-text filter over title + 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	Keep only releases whose tagName contains this.
`sort`	No	Sort field; prefix '-' for descending.
`limit`	No	Return at most N (e.g. last 3 releases).
`fields`	No	Return only these top-level fields (plus id keys), narrowing the response further.
`project`	Yes
`preRelease`	No	true = only pre-releases, false = only stable.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.1Nov 13, 2026

TDQS

C2.4/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that — it says nothing about the default slim view versus the raw flag, filtering, or result size limits, all of which are real behaviors of this tool.

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?

Two words with no wasted phrasing, but this is under-specification rather than conciseness; there is no front-loaded scope, no filtering hint, and nothing for an agent to act on beyond the name.

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?

With 8 parameters (including response-shaping options like raw and fields) and no output schema, the description should at least note that results are slimmed by default and can be filtered. None of that context is present, so an agent must read the whole schema to call this correctly.

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?

Schema description coverage is 88%, so the schema already explains q, tag, sort, limit, fields, raw, and preRelease in detail. The description contributes no additional parameter meaning, which is acceptable at this coverage level but earns only the baseline.

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?

"List releases" names a specific verb and resource, so the basic action is unambiguous. But it does nothing to separate this from siblings such as gitflic_release_latest or gitflic_release_get, leaving an agent to infer the difference from names alone.

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 mention of alternatives, and no prerequisites (e.g. that a project is required). Usage is only implied by the word "List".

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

Deploy Server