GitFlic MCP Server

gitflic_mr_diff

Read-only

Retrieves file-level diffs for a GitFlic merge request, returning hunks and per-line annotations so you can review exactly what changed in each file.

Instructions

Get the file-level diff for a merge request (hunks + per-line annotations).

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

Input Schema

Name	Required	Description
`id`	Yes
`all`	No	Fetch all pages. Defaults to true when page is omitted.
`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.
`page`	No	Zero-based page index; selects one page unless all is true.
`size`	No	Requested page size; server limits are respected.
`expand`	No	Expand collapsed text diffs; defaults to true.
`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

B3.3/5.0

Behavior3/5

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

Annotations already declare this as a non-destructive read with openWorldHint, so the safety profile is covered. The description contributes only the response shape (hunks plus per-line annotations), which is valuable since no output schema exists, but says nothing about pagination behavior, slimming/token compression, or how large diffs are truncated.

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

Conciseness5/5

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

A single front-loaded sentence with zero filler. The parenthetical adds information rather than restating the name.

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?

With eight parameters, no output schema, and pagination/compression behavior in play, the description is thin. It names the return contents but leaves the agent to discover paging defaults, slimming effects, and required identifiers (project, id) entirely from the schema.

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 75%, so the schema already documents all, raw, page, size, expand, and fields in detail. The description adds no parameter meaning whatsoever, which meets the baseline of 3 for well-covered schemas but does not exceed it.

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 the file-level diff for a merge request") and names the payload contents (hunks, per-line annotations). It is distinguishable from gitflic_mr_view or gitflic_blob_get by the word "diff", but it does not explicitly contrast itself with any sibling.

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 or when-not-to-use guidance at all. Nothing tells the agent whether to prefer this over gitflic_mr_view for reviewing changes, or when a raw/full fetch is warranted beyond the schema's own note on the raw parameter.

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

Deploy Server