Skip to main content
Glama

Create Downstream Reference

create_reference

Add downstream references between Codebeamer items to establish derivation and traceability links, such as connecting requirements to their source items.

Instructions

Add a downstream reference from one Codebeamer item to another. Downstream references represent derivation/traceability links (e.g. a requirement derived from another). The 'from' item gets the downstream reference pointing to the 'to' item.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fromItemIdYesItem ID that will have the downstream reference added
toItemIdYesItem ID to reference as downstream

Implementation Reference

  • The handler function for 'create_reference', which invokes the client's createDownstreamReference method.
    async ({ fromItemId, toItemId }) => {
      await client.createDownstreamReference(fromItemId, toItemId);
      const text =
        `**Downstream reference created**\n\n` +
        `| Field | Value |\n|---|---|\n` +
        `| Upstream (from) | #${fromItemId} |\n` +
        `| Downstream (to) | #${toItemId} |`;
      return { content: [{ type: "text", text }] };
    },
  • The schema definition for the 'create_reference' tool inputs.
    {
      title: "Create Downstream Reference",
      description:
        "Add a downstream reference from one Codebeamer item to another. " +
        "Downstream references represent derivation/traceability links (e.g. a requirement derived from another). " +
        "The 'from' item gets the downstream reference pointing to the 'to' item.",
      inputSchema: {
        fromItemId: z
          .number()
          .int()
          .positive()
          .describe("Item ID that will have the downstream reference added"),
        toItemId: z
          .number()
          .int()
          .positive()
          .describe("Item ID to reference as downstream"),
      },
    },
  • The registration of the 'create_reference' tool in the MCP server.
    server.registerTool(
      "create_reference",
      {
        title: "Create Downstream Reference",
        description:
          "Add a downstream reference from one Codebeamer item to another. " +
          "Downstream references represent derivation/traceability links (e.g. a requirement derived from another). " +
          "The 'from' item gets the downstream reference pointing to the 'to' item.",
        inputSchema: {
          fromItemId: z
            .number()
            .int()
            .positive()
            .describe("Item ID that will have the downstream reference added"),
          toItemId: z
            .number()
            .int()
            .positive()
            .describe("Item ID to reference as downstream"),
        },
      },
      async ({ fromItemId, toItemId }) => {
        await client.createDownstreamReference(fromItemId, toItemId);
        const text =
          `**Downstream reference created**\n\n` +
          `| Field | Value |\n|---|---|\n` +
          `| Upstream (from) | #${fromItemId} |\n` +
          `| Downstream (to) | #${toItemId} |`;
        return { content: [{ type: "text", text }] };
      },
    );
Behavior3/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 clearly indicates this is a write operation ('Add a downstream reference') and explains the directional nature of the relationship. However, it doesn't mention permission requirements, whether the operation is idempotent, what happens if the reference already exists, or what the response looks like. It provides basic behavioral context but lacks important operational details.

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 perfectly concise with just two sentences. The first sentence states the action and its purpose, while the second clarifies the directional semantics. Every word contributes meaning without redundancy, and the information is front-loaded effectively.

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

Completeness3/5

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

For a mutation tool with no annotations and no output schema, the description provides adequate basic information about what the tool does and the relationship it creates. However, it lacks important contextual details like permission requirements, error conditions, or what constitutes a successful operation. The description is complete enough to understand the tool's purpose but insufficient for fully informed usage.

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%, so the schema already fully documents both parameters. The description adds some semantic context by explaining that 'fromItemId' gets the reference added and 'toItemId' is referenced as downstream, but this doesn't significantly enhance understanding beyond what the schema provides. The baseline score of 3 is appropriate given the comprehensive schema coverage.

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 specific action ('Add a downstream reference'), identifies the resources involved ('from one Codebeamer item to another'), and explains the semantic meaning of this type of reference ('represent derivation/traceability links'). It distinguishes this tool from sibling tools like 'create_association' or 'create_item' by specifying it creates a particular type of relationship between items.

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 context by explaining what downstream references represent ('derivation/traceability links'), which suggests when this tool might be appropriate. However, it doesn't explicitly state when to use this tool versus alternatives like 'create_association' or provide any exclusion criteria. The guidance is helpful but not comprehensive.

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