GitFlic MCP Server

gitflic_auth_list

Read-only

List all known GitFlic accounts with masked tokens and mark the active one, so you can confirm available identities before switching or binding.

Instructions

List all known accounts (default + named) with masked token values. Marks the active account with '*'. Use before switching or binding to confirm available identities.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gitflic_auth_list"
  }
}

Input Schema

Name	Required	Description	Default
`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.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.1Nov 13, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the read-only safety profile is covered upstream. The description still earns credit for disclosing behavior not in the annotations: tokens are masked in the output, the active account is flagged with '*', and both default and named accounts are included. It does not mention ordering or whether a disabled/unauthenticated state changes the listing.

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?

Three short sentences, front-loaded with what the tool returns before adding the workflow hint. Every sentence contributes distinct information with no filler or restatement of the title.

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

Completeness5/5

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

For a zero-required-parameter, read-only listing tool with annotations covering safety, no output schema, and 100% param coverage, nothing essential is missing. Output shape and intended pre-flight use are both stated, which is all an agent needs to invoke it 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?

Both parameters (raw, fields) have full schema descriptions, so the schema fully carries their meaning. The description adds no information about raw or fields, so the documented baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb and resource ('List all known accounts'), defines the scope ('default + named'), and describes the observable output shape (masked token values, '*' on the active account). This is distinguishable at a glance from siblings like auth_switch or auth_bind, which mutate or select rather than enumerate.

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?

Gives explicit when-to-use guidance: 'Use before switching or binding to confirm available identities,' which ties the tool to the concrete sibling workflows of switching and binding. It stops short of stating when not to use it or naming the sibling tools directly, so it is clear rather than exhaustive.

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

Deploy Server