Skip to main content
Glama
Sign In
GitFlic MCP Server

GitFlic MCP Server

by zhimbura
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gitflic_user_search

Read-only

Find GitFlic users by username substring to identify accounts, resolve IDs for assignments, or look up profiles. Returns slim results; request extra fields or raw output as needed.

Instructions

Search users by username substring.

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

Input Schema

NameRequiredDescriptionDefault
qYes
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

A3.5/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 the meaningful behavioral fact that matching is by substring (partial, potentially multi-result), but says nothing about result ordering, caps, or pagination — notable since idempotentHint=false hints at variable results.

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?

A single front-loaded sentence with no filler, which suits a simple search tool. It is arguably under-specified rather than padded, but nothing is wasted.

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 three-parameter, non-destructive read with no output schema, the description plus annotations and schema together are close to sufficient. The remaining gap is how many results come back and whether the substring match is literal or fuzzy.

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?

At 67% schema coverage, the undocumented parameter is exactly 'q', and the description fills that gap by explaining it matches a username substring. However, it adds no detail on case sensitivity, minimum length, or empty-query behavior, so it does the minimum rather than fully compensating.

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 (Search) and resource (users) plus the matching key (username substring), so the agent knows it performs a partial-match lookup rather than an exact fetch. It doesn't explicitly contrast with gitflic_user_get, but the 'substring' framing makes the distinction inferable.

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 'by username substring' phrasing implies usage when the exact username is unknown, but there is no explicit when-to-use, when-not-to-use, or named alternative such as the exact-user lookup sibling. Guidance is implied rather than stated.

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