Skip to main content
Glama

Get Project

get_project

Fetch full project details from Codebeamer by providing the project's numeric ID. Returns all relevant project data for integration or review.

Instructions

Get full details for a single Codebeamer project by its numeric ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesNumeric Codebeamer project ID

Implementation Reference

  • The handler function that executes the 'get_project' tool logic. It calls client.getProject(projectId) and formats the result.
      async ({ projectId }) => {
        const project = await client.getProject(projectId);
        return { content: [{ type: "text", text: formatProject(project) }] };
      },
    );
  • Input schema for 'get_project': defines a required 'projectId' positive integer.
    inputSchema: {
      projectId: z
        .number()
        .int()
        .positive()
        .describe("Numeric Codebeamer project ID"),
    },
  • Registration of the 'get_project' tool via server.registerTool() within registerProjectTools().
    server.registerTool(
      "get_project",
      {
        title: "Get Project",
        description:
          "Get full details for a single Codebeamer project by its numeric ID.",
        inputSchema: {
          projectId: z
            .number()
            .int()
            .positive()
            .describe("Numeric Codebeamer project ID"),
        },
      },
      async ({ projectId }) => {
        const project = await client.getProject(projectId);
        return { content: [{ type: "text", text: formatProject(project) }] };
      },
    );
  • Helper formatter that converts a CbProject object into a formatted markdown string for display.
    export function formatProject(project: CbProject): string {
      const lines: string[] = [
        `## ${project.name}`,
        "",
        `- **ID:** ${project.id}`,
        `- **Key:** ${project.keyName ?? "-"}`,
        `- **Status:** ${project.closed ? "Closed" : "Open"}`,
      ];
    
      if (project.category) {
        lines.push(`- **Category:** ${project.category}`);
      }
      if (project.description) {
        lines.push("", "### Description", "", project.description);
      }
      if (project.createdAt) {
        lines.push(`- **Created:** ${project.createdAt}`);
      }
    
      return lines.join("\n");
    }
  • Client method getProject() that sends a GET request to /projects/{id} to fetch a project from the API.
    getProject(id: number): Promise<CbProject> {
      return this.http.get(`/projects/${id}`, { resource: `project ${id}` });
    }
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 only states 'Get full details' without specifying what details are included, any authentication requirements, or side effects. This leaves the agent with limited behavioral context.

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, front-loaded sentence of 12 words with no unnecessary information. Every word earns its place for a simple ID lookup tool.

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's simplicity (one parameter, no output schema, no nested objects), the description is mostly complete. However, it does not clarify what 'full details' entails, which slightly reduces completeness.

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 coverage is 100%, and the description repeats the schema's 'numeric ID' aspect but adds no new semantics about the parameter beyond what the schema provides. Baseline 3 is appropriate.

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?

The description clearly states the verb 'Get', the resource 'full details for a single Codebeamer project', and the identifier method 'by its numeric ID'. This distinguishes it from sibling tools like get_item, get_tracker, and list_projects.

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 description implies usage when needing project details by ID but does not provide explicit when-to-use or when-not-to-use guidance, nor does it reference alternatives like list_projects for browsing.

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