GitFlic MCP Server

gitflic_auth_switch

DestructiveIdempotent

Switch the active GitFlic account so later calls without project bindings use that account's token; fails if no token is stored for the named account.

Instructions

Make the active account. Subsequent tool calls without a per-project binding resolve to this account's token. Refuses if no token is stored for the named account.

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": {
      "name": "<name>"
    },
    "name": "gitflic_auth_switch"
  }
}

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.
`name`	Yes	Account name to activate

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.1Nov 13, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Beyond annotations, the description adds meaningful behavior: the switch affects subsequent token resolution only where no per-project binding exists, and the tool refuses if the named account has no stored token. This is consistent with destructiveHint=true and idempotentHint=true, and no contradiction is present.

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?

The description is three short sentences with zero waste. The core action is front-loaded, followed by scoping behavior and the refusal condition.

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?

For a two-parameter auth-switching tool with annotations covering safety traits and no output schema, the description supplies the essential behavioral context. It could be slightly more complete by explicitly naming when to use it versus sibling auth operations.

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 the schema already documents both parameters, including the raw flag. The description reinforces that name is the account to activate but adds no syntax or format details beyond the schema.

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?

The description states a specific verb and resource: make a named account the active account. It also clarifies the effect on subsequent token resolution. It does not explicitly distinguish itself from sibling auth tools such as login, bind, or logout, which keeps it from a 5.

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

Usage Guidelines3/5

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

The description implies usage by explaining that subsequent calls without a per-project binding will resolve to this account's token, and it states a refusal precondition. However, it does not explicitly say when to use this instead of auth_login, auth_bind, or auth_list.

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

Deploy Server