GitFlic MCP Server

gitflic_blob_get

Read-only

Retrieve a file's text content from a GitFlic repository at a branch or commit; binary files are returned base64-encoded so you can inspect any file.

Instructions

Get a file's text content. Binary files are base64-encoded by the server.

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>",
      "path": "<path>"
    },
    "name": "gitflic_blob_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.
`path`	Yes	File path inside the repo, e.g. 'README.md'
`branch`	No
`commit`	No
`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.9/5.0

Behavior3/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 safety is covered. The description adds one genuinely useful behavioral fact beyond them: binary files are returned base64-encoded by the server, which tells the agent to expect non-UTF-8 payloads. It omits ref resolution behavior and any auth or error semantics.

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?

Two short sentences with the core purpose front-loaded and zero filler. Brevity here is efficient rather than padded, though it edges toward under-specification for a six-parameter tool.

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?

No output schema exists, six parameters with only half documented, and no explanation of how branch versus commit resolves the read. For a content-fetch tool with ambiguous ref parameters, the description leaves too much for the agent to infer.

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%, with branch, commit, and project entirely undocumented in the schema, and the description adds no meaning for any of the six parameters. With half the parameters undescribed, the description should have compensated by explaining ref selection, but it does not.

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 a file's text content'. It is clear what the tool returns, but it never names or contrasts the closest sibling (gitflic_blob_files) or any other content-retrieval tool, so differentiation is left to the agent.

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 alternatives, and no mention of prerequisites such as which ref selector to use. The schema exposes branch, commit, and project, but the description never says whether branch and commit are mutually exclusive or which one defaults.

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

Deploy Server