Skip to main content
Glama
concurrence-hq

forge-mcp

by concurrence-hq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

forge_unit_test_set_create

Create a unit test set by specifying a name, description, test runs, and tags, to execute multiple unit tests together in one coordinated run.

Instructions

Create a new unit test set (collection of unit tests to run together).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName for the unit test set
tagsYesTags (alphanumeric keys and values, no hyphens or special characters)
org_idNoOrg ID (uses active org if omitted)
descriptionYesDescription of the unit test set (null if none)
unit_test_runsYesUnit test runs included in this set

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.14
    • removedInput schema / properties / description / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / description / type
      Added value: +[
+  "string",
+  "null"
+]
  2. First observedv0.1.13

TDQS

B3.2/5.0
Behavior2/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 of behavioral disclosure. It only states that a new set is created and gives no information about side effects, required permissions, idempotency, validation outcomes, or what happens on success or failure.

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 clear sentence with no redundant wording. The core purpose is front-loaded and every word contributes to understanding the tool.

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?

Despite rich schema coverage, the tool has no annotations. No output schema, no explanation of return values, and no contextual details about how org_id behaves or when this set should be used. For a tool with nested parameters and a create action, this description is too sparse to be considered complete.

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 baseline is 3. The parenthetical 'collection of unit tests to run together' adds mild context for the unit_test_runs parameter, but the description otherwise adds no meaning beyond what the schema already documents for each parameter.

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 names a specific action ('Create') and a specific resource ('unit test set'), and clarifies that a set is a collection of unit tests run together. This distinguishes the tool from the sibling forge_unit_test_create, which creates an individual test, and from forge_unit_test_set_update, which modifies an existing set. The purpose is immediately clear.

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?

The description offers no guidance on when to use this tool versus alternatives like forge_unit_test_set_update or forge_unit_test_create. It simply states that it creates a new set, leaving usage decisions entirely to inference from the tool name and schema.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools