Skip to main content
Glama

Get User

get_user

Retrieve profile details for any Codebeamer user by providing their numeric user ID.

Instructions

Get profile details for a Codebeamer user by their numeric ID. User IDs appear in item fields like assignedTo and createdBy.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userIdYesNumeric user ID

Implementation Reference

  • The async handler function that executes the 'get_user' tool logic. It calls client.getUser(userId) and formats the result.
    async ({ userId }) => {
      const user = await client.getUser(userId);
      return { content: [{ type: "text", text: formatUser(user) }] };
    },
  • Input schema for the 'get_user' tool, defined with zod: userId is a positive integer.
    inputSchema: {
      userId: z.number().int().positive().describe("Numeric user ID"),
    },
  • Registration of the 'get_user' tool via server.registerTool with title, description, inputSchema, and handler.
    server.registerTool(
      "get_user",
      {
        title: "Get User",
        description:
          "Get profile details for a Codebeamer user by their numeric ID. " +
          "User IDs appear in item fields like assignedTo and createdBy.",
        inputSchema: {
          userId: z.number().int().positive().describe("Numeric user ID"),
        },
      },
      async ({ userId }) => {
        const user = await client.getUser(userId);
        return { content: [{ type: "text", text: formatUser(user) }] };
      },
    );
  • Client method getUser(id) that makes an HTTP GET request to /users/{id}.
    getUser(id: number): Promise<CbUser> {
      return this.http.get(`/users/${id}`, { resource: `user ${id}` });
    }
  • The CbUser interface type definition specifying the structure of a user object.
    export interface CbUser {
      id: number;
      name: string;
      firstName?: string;
      lastName?: string;
      email?: string;
      status?: string;
      registryDate?: string;
    }
Behavior3/5

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

No annotations are present, so the description must disclose behavior. It states it retrieves profile details, implying a read operation, but does not explicitly confirm read-only nature, mention authentication requirements, or describe the output. It is minimally adequate but lacks depth.

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 sentences with no wasted words. The first sentence immediately conveys purpose, and the second provides critical context. Ideal length for quick agent scanning.

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?

Given the tool has one parameter, no output schema, and no annotations, the description covers the core purpose and parameter source adequately. Missing return value details, but for a simple read operation, the information is practically sufficient. Slightly above average due to the practical ID context.

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?

Schema has 100% coverage with a description for userId ('Numeric user ID'). The tool description adds value by explaining where to find user IDs (in assignedTo and createdBy fields), which aids the agent in constructing valid input. This extra context justifies a score above baseline 3.

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

Purpose5/5

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

Description clearly states 'Get profile details for a Codebeamer user by their numeric ID', specifying verb+resource. It distinguishes from sibling tools (e.g., get_item, get_project) by focusing on user profiles. No ambiguity.

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?

Provides clear context on when to use: when you have a numeric user ID from item fields like assignedTo or createdBy. It doesn't explicitly mention alternatives or when not to use, but the context is strong enough for an agent to infer appropriate usage.

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/3KniGHtcZ/codebeamer-mcp'

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