Skip to main content
Glama

Get Item

get_item

Retrieve a lightweight summary of a Codebeamer work item including ID, name, tracker, status, and description. Identify and read an item's basic information without extra details.

Instructions

Get a lightweight summary of a Codebeamer work item: ID, name, tracker, status and description. Use this when you only need to identify the item and read its description. For priority, assignees, dates, story points, custom fields and test steps, call get_item_details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemIdYesNumeric item (work item) ID

Implementation Reference

  • Registration of the 'get_item' tool using the MCP server.registerTool method. Defines input schema (itemId: positive integer) and description.
    server.registerTool(
      "get_item",
      {
        title: "Get Item",
        description:
          "Get a lightweight summary of a Codebeamer work item: ID, name, tracker, status and description. " +
          "Use this when you only need to identify the item and read its description. " +
          "For priority, assignees, dates, story points, custom fields and test steps, call get_item_details.",
        inputSchema: {
          itemId: z
            .number()
            .int()
            .positive()
            .describe("Numeric item (work item) ID"),
        },
      },
      async ({ itemId }) => {
        const item = await client.getItem(itemId);
        return { content: [{ type: "text", text: formatItemSummary(item) }] };
      },
    );
  • Handler function for the 'get_item' tool. Calls client.getItem(itemId) and formats the result using formatItemSummary.
    async ({ itemId }) => {
      const item = await client.getItem(itemId);
      return { content: [{ type: "text", text: formatItemSummary(item) }] };
    },
  • Client method that makes the actual HTTP GET request to /items/{id} to fetch a CbItem.
    getItem(id: number): Promise<CbItem> {
      return this.http.get(`/items/${id}`, { resource: `item ${id}` });
  • Formatter function that produces the human-readable summary output for a single item (ID, name, tracker, type, status, description).
    export function formatItemSummary(item: CbItem): string {
      const lines: string[] = [
        `## [${item.id}] ${item.name}`,
        "",
        `- **Tracker:** ${item.tracker?.name ?? "?"} (ID: ${item.tracker?.id ?? "?"})`,
        `- **Type:** ${item.categories?.[0]?.name ?? item.typeName ?? "?"}`,
        `- **Status:** ${item.status?.name ?? "?"}`,
      ];
    
      const description =
        typeof item.description === "string"
          ? item.description
          : item.description?.value ?? item.description?.markup;
      if (description) {
        lines.push("", "### Description", "", description);
      }
    
      return lines.join("\n");
    }
  • Input schema for the 'get_item' tool: itemId must be a positive integer.
    inputSchema: {
      itemId: z
        .number()
        .int()
        .positive()
        .describe("Numeric item (work item) ID"),
    },
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It accurately implies a read-only, low-cost operation by describing a 'lightweight summary'. Missing details on permissions or rate limits, but for a simple read tool this is acceptable.

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, no redundant words, front-loaded with the action and output. Efficient for an agent to quickly understand.

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

Completeness5/5

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

For a simple retrieval tool with one parameter and no output schema, the description fully covers what the agent needs: what fields are returned and when to use it vs. the alternative. No gaps.

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?

Only one parameter (itemId) with full schema coverage. Description does not add extra meaning beyond the schema's description ('Numeric item (work item) ID'), which is already clear. Baseline score of 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?

Description clearly states it returns a lightweight summary of a Codebeamer work item with specific fields (ID, name, tracker, status, description). It explicitly distinguishes from sibling get_item_details by noting what it lacks (priority, assignees, dates, etc.).

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

Usage Guidelines5/5

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

Directly tells the agent when to use this tool ('when you only need to identify the item and read its description') and when not to, pointing to get_item_details as the alternative for more extensive information.

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