Skip to main content
Glama

获取当前用户

gitea_user_current

Retrieve details about the currently authenticated user in Gitea, including profile information and account status.

Instructions

Get information about the currently authenticated user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:546-586 (registration)
    Registers the 'gitea_user_current' MCP tool. Includes the tool schema (title and description, no input parameters), and the inline handler function that calls GiteaClient.getCurrentUser() and returns formatted user information or error.
    mcpServer.registerTool(
      'gitea_user_current',
      {
        title: '获取当前用户',
        description: 'Get information about the currently authenticated user',
      },
      async (_args: any, _extra: any) => {
        try {
          const user = await ctx.client.getCurrentUser();
          return {
            content: [
              {
                type: 'text' as const,
                text: JSON.stringify(
                  {
                    id: user.id,
                    login: user.login,
                    full_name: user.full_name,
                    email: user.email,
                    avatar_url: user.avatar_url,
                  },
                  null,
                  2
                ),
              },
            ],
          };
        } catch (error: unknown) {
          const errorMessage = error instanceof Error ? error.message : String(error);
          return {
            content: [
              {
                type: 'text' as const,
                text: `Error: ${errorMessage}`,
              },
            ],
            isError: true,
          };
        }
      }
    );
  • Implementation of GiteaClient.getCurrentUser() method, which performs a GET request to the Gitea API endpoint '/api/v1/user' to retrieve the current authenticated user's information.
    /**
     * 获取当前认证用户信息
     */
    async getCurrentUser(): Promise<{
      id: number;
      login: string;
      full_name: string;
      email: string;
      avatar_url: string;
    }> {
      return this.get('/user');
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action but lacks details on permissions needed, rate limits, error conditions, or what specific user information is returned. This is inadequate for a tool that likely involves authentication and data retrieval.

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 a single, clear sentence with no wasted words. It's front-loaded with the core purpose and efficiently communicates the essential action without unnecessary elaboration.

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?

Given the lack of annotations and output schema, the description is insufficient. It doesn't explain what 'information' includes (e.g., username, email, permissions) or the response format, leaving gaps for an agent to understand the tool's full behavior and output.

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

Parameters4/5

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

The tool has 0 parameters, and the input schema has 100% description coverage (though empty). The description doesn't need to add parameter details, so it meets the baseline for a parameterless tool by not introducing confusion.

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 clearly states the verb ('Get') and resource ('information about the currently authenticated user'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'gitea_context_get' which might also retrieve user context, leaving room for potential confusion.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't specify if this should be used for authentication checks, user profile retrieval, or other contexts, nor does it mention prerequisites like requiring an active session.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SupenBysz/gitea-mcp-tool'

If you have feedback or need assistance with the MCP directory API, please join our Discord server