Skip to main content
Glama

get_user

Retrieve user information from Gitee by specifying a username. Use this tool to access user details for repository management or integration purposes.

Instructions

获取 Gitee 用户信息

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
usernameYesUsername

Implementation Reference

  • The main handler function that fetches the specified Gitee user's information using the API.
    export async function getUser(username: string) {
      username = validateOwnerName(username);
    
      const url = `/users/${username}`;
      const response = await giteeRequest(url, "GET");
    
      return GiteeUserSchema.parse(response);
    }
  • Zod schema defining the input parameters for the get_user tool (username).
    export const GetUserSchema = z.object({
      // 用户名
      username: z.string().describe("Username"),
    });
  • index.ts:253-261 (registration)
    Registers the get_user tool with the MCP server, linking schema and handler.
    server.registerTool({
      name: "get_user",
      description: "获取 Gitee 用户信息",
      schema: userOperations.GetUserSchema,
      handler: async (params: any) => {
        const { username } = params;
        return await userOperations.getUser(username);
      },
    });
Behavior2/5

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

No annotations are provided, so the description carries full burden. It implies a read-only operation ('get'), but doesn't disclose behavioral traits like authentication requirements, rate limits, error handling, or what happens with invalid usernames. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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?

The description is a single, efficient sentence in Chinese, front-loaded with the core purpose. It's appropriately sized for a simple tool, with no wasted words, though it could be slightly more informative without losing conciseness.

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 tool's complexity (simple read operation), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what user information is returned, potential errors, or authentication needs. For a tool interacting with an external API like Gitee, more context is needed to use it effectively.

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%, with the parameter 'username' documented in the schema. The description doesn't add any meaning beyond the schema, such as format constraints or examples. With high schema coverage, the baseline is 3, as the description doesn't compensate but also doesn't detract.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description '获取 Gitee 用户信息' (Get Gitee user information) states a clear verb ('get') and resource ('user information'), but it's vague about what specific information is retrieved. It distinguishes from siblings like get_current_user, get_issue, etc., but doesn't specify how it differs from get_current_user beyond the username parameter requirement.

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. It doesn't mention prerequisites, such as needing a valid username, or differentiate from get_current_user (which likely retrieves the authenticated user's info without a parameter). The description alone offers no usage context.

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

Related 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/normal-coder/gitee-mcp-server'

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