GitFlic MCP Server

gitflic_branch_default

Read-only

Retrieves the default branch for a specified GitFlic project, helping you identify the base branch for cloning, comparisons, or merge request targeting.

Instructions

Get the project's default branch.

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

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.
`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.8/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered without the description. The description adds nothing beyond the bare verb: no return shape, no behavior when a project has no default branch, and no note on the token/slimming behavior that the 'raw' parameter implies.

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

Conciseness4/5

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

A single front-loaded sentence with no filler or redundancy. It is tight, but the tightness comes partly from under-specification rather than disciplined editing.

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?

This is a simple read tool with annotations covering safety and no output schema to explain, so the burden is modest. Still, the missing semantics for the required 'project' identifier and the absence of any return-value hint leave a real gap for an agent trying to call it correctly on the first attempt.

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 67%, and the two documented parameters (raw, fields) carry their own descriptions in the schema. The one required parameter, 'project', is completely undocumented in both schema and description, so an agent gets no signal whether it takes a slug, path, or numeric ID.

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' plus 'the project's default branch'. That is distinct enough from siblings like gitflic_branch_list or gitflic_branch_get, which operate on arbitrary branches, though the description never explicitly contrasts with them.

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 prerequisites, and no named alternative. The agent must infer that this is the right call when it needs the default branch name rather than a specific branch or a full listing.

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

Deploy Server