Skip to main content
Glama
lleontor705

forgespec-mcp

by lleontor705
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

tb_add_task

Add a task to an existing board with a spec reference and acceptance criteria to ensure traceable, criteria-driven work items.

Instructions

Add a task to an existing board. Every task should reference a spec and have acceptance criteria.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actorNo
gatesNo
titleYesTask title
board_idYesBoard ID
priorityNoPriority: p0 (critical), p1 (high), p2 (medium), p3 (low)p2
spec_refNoReference to spec document
work_unitNo
capabilityNo
api_versionNo
descriptionNoTask description
dependenciesNoTask IDs this task depends on
schema_versionNo
idempotency_keyNo
coordination_modeNo
acceptance_criteriaNoAcceptance criteria for completion
expected_board_revisionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv1.6.0
    • addedInput schema / properties / actor
      Added value: +{
+  "maxLength": 256,
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / api_version
      Added value: +{
+  "maxLength": 32,
+  "type": "string"
+}
    • addedInput schema / properties / capability
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "apiVersion": {
+      "const": "1.0.0",
+      "type": "string"
+    },
+    "coordinationMode": {
+      "const": "direct-v1",
+      "type": "string"
+    },
+    "negotiated": {
+      "items": {
+        "maxLength": 128,
+        "minLength": 1,
+        "type": "string"
+      },
+      "maxItems": 100,
+      "minItems": 1,
+      "type": "array"
+    },
+    "schemaVersion": {
+      "const": "1.0.0",
+      "type": "string"
+    }
+  },
+  "required": [
+    "coordinationMode",
+    "apiVersion",
+    "schemaVersion",
+    "negotiated"
+  ],
+  "type": "object"
+}
    • addedInput schema / properties / coordination_mode
      Added value: +{
+  "enum": [
+    "legacy",
+    "direct-v1"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / expected_board_revision
      Added value: +{
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / gates
      Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "allowed_actors": {
+        "items": {
+          "maxLength": 256,
+          "minLength": 1,
+          "type": "string"
+        },
+        "maxItems": 100,
+        "minItems": 1,
+        "type": "array"
+      },
+      "gate_id": {
+        "maxLength": 128,
+        "minLength": 1,
+        "type": "string"
+      },
+      "required_for": {
+        "items": {
+          "enum": [
+            "backlog",
+            "ready",
+            "in_progress",
+            "in_review",
+            "done",
+            "blocked"
+          ],
+          "type": "string"
+        },
+        "maxItems": 6,
+        "minItems": 1,
+        "type": "array"
+      }
+    },
+    "required": [
+      "gate_id",
+      "required_for",
+      "allowed_actors"
+    ],
+    "type": "object"
+  },
+  "maxItems": 20,
+  "type": "array"
+}
    • addedInput schema / properties / idempotency_key
      Added value: +{
+  "maxLength": 256,
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / schema_version
      Added value: +{
+  "maxLength": 32,
+  "type": "string"
+}
    • addedInput schema / properties / work_unit
      Added value: +{
+  "maxLength": 128,
+  "minLength": 1,
+  "type": "string"
+}
  2. First observedv1.2.2

TDQS

B3/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. It only reveals the basic add action and that the board should already exist; it does not disclose concurrency, idempotency, validation failures, permission requirements, or effects of missing board_id. This is insufficient for a mutation tool.

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 two short sentences with no filler. It is front-loaded and every sentence contributes useful information.

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?

For a tool with 16 parameters, nested gates and capability objects, no output schema, and no annotations, this description is too sparse. It covers the core purpose but omits essential contextual details such as how gates work, idempotency methods, revision handling, and task creation rules beyond the 'should' note.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 44%, and the text does little to compensate. 'Reference a spec and have acceptance criteria' gives some meaning to spec_ref and acceptance_criteria, but most parameters, including gates, capability, work_unit, expected_board_revision, and coordination_mode, are left without added meaning beyond their names.

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

Purpose4/5

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

Description clearly states the action ('Add a task') and target ('an existing board'), which is specific and unambiguous. It does not explicitly name sibling alternatives, but 'add' is enough to distinguish from update/claim/query tools.

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 sentence 'Every task should reference a spec and have acceptance criteria' gives useful usage guidance about how tasks should be created. However, it does not explicitly describe when to use this tool versus alternatives, nor are exclusions or prerequisites beyond board existence mentioned.

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