GitFlic MCP Server

gitflic_project_resolve

Read-onlyIdempotent

Resolve a project owner/alias to its UUID and default branch, using a local cache, so subsequent GitFlic API calls have the identifiers they require.

Instructions

Resolve a project owner/alias to its UUID + defaultBranch. Cached locally; needed before most other calls.

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

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	owner/alias, e.g. 'tikhon/wave'

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.1Nov 13, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuine context beyond them: results are cached locally, which signals possible staleness, and it names the two fields returned. It does not say how the cache is invalidated or what happens on a miss.

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?

Two short sentences, both front-loaded with the most decision-relevant facts: what it resolves to first, then the prerequisite/caching note. Nothing is wasted or buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, but the description states the returned values (UUID + defaultBranch), which compensates. For a small three-parameter resolution tool with full annotation coverage this is nearly complete; only cache lifetime behavior is left unstated.

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 100%, so all three parameters (project, raw, fields) are already documented in the schema. The description only restates the 'owner/alias' form already present in the project parameter, adding no syntax or format detail beyond it — baseline 3.

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?

Uses a specific verb ('Resolve') and names both the input (project owner/alias) and the output (UUID + defaultBranch), which is more precise than the sibling gitflic_project_get. It stops short of explicitly contrasting itself with that sibling, so an agent must infer the distinction from the name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Needed before most other calls' gives a clear prerequisite-style usage cue that an agent can act on. It offers no explicit when-not or named alternative (e.g. when to use gitflic_project_get instead), so it falls short of full routing guidance.

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

Deploy Server