Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Gitea: Get user

gitea_get_user
Read-only

Retrieve detailed information about a Gitea user by username, enabling profile lookups and user management on a specified site.

Instructions

[UNIFIED] Get information about a Gitea user by username.

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": {
      "site": "<site>",
      "username": "<username>"
    },
    "name": "gitea_get_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
usernameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0
  2. Removedv3.13.1
  3. First observedv3.4.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, so the safety profile needs no restatement, yet the description contributes nothing further: no note about authentication needs, whether private user fields are returned, or what happens when the username does not exist. It effectively paraphrases the title.

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 well-formed sentence with no padding, and the resource is front-loaded. The bracketed '[UNIFIED]' tag is wasted leading text that conveys nothing to an agent.

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

Completeness2/5

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

With no output schema and no annotation detail beyond read-only, the description should at least say what a user object covers and what a not-found result looks like. It also leaves the 'site' parameter unexplained, so the definition is thin for even a simple two-parameter fetch.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so both parameters depend on the description for meaning. The phrase 'by username' clarifies one parameter, but 'site' — presumably which Gitea instance to target and a likely source of failed calls — is never explained.

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 ('Get information about a Gitea user') and adds the lookup key ('by username'), which is enough for an agent to distinguish a single-user fetch from list/mutation siblings. The opaque '[UNIFIED]' prefix adds no information, and the description does not explicitly contrast with lookups like supabase_get_user_by_email.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. The only usable signal is the implied 'call this when you know a username rather than an email/ID', which the agent must infer.

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