Skip to main content
Glama
Sign In
GitFlic MCP Server

GitFlic MCP Server

by zhimbura
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gitflic_auth

Read-only

Verify GitFlic authentication: retrieve the current user's ID, username, email, and full name to confirm your API token works.

Instructions

Check authentication: returns the current authenticated user (id, username, email, fullName). Use this first to verify the token works.

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

Input Schema

NameRequiredDescriptionDefault
rawNoReturn the full, un-slimmed GitFlic response for THIS call (no token compression). Use when the default slim view dropped a field you need.
fieldsNoReturn only these top-level fields (plus id keys), narrowing the response further.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds context those annotations do not carry: the call is a token-validity probe and returns a specific identity payload, which helps an agent interpret the result. It does not say what happens on an invalid or expired token, which is the main remaining behavioral gap.

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, front-loaded with the action and its return shape, followed by the routing hint. No filler and nothing 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, so the description usefully enumerates the returned identity fields, which compensates well for a two-parameter read-only tool. It stops short of noting failure behavior or that raw/fields affect the response shape, but an agent has what it needs to call 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?

Schema description coverage is 100%, so both optional parameters (raw, fields) are already fully explained in the schema, including the meaning of raw. The description adds nothing about parameters, so the baseline 3 applies rather than a higher score.

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 ("Check authentication") and immediately names the payload returned: id, username, email, fullName. That is far more precise than the bare name gitflic_auth, though it never distinguishes itself explicitly from siblings such as gitflic_auth_list or gitflic_auth_bind.

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?

"Use this first to verify the token works" gives clear sequencing guidance that an agent can act on before calling other GitFlic tools. It offers no exclusions or named alternatives, so it falls short of the explicit when/when-not pattern.

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

Deploy Server

Other Tools