Skip to main content
Glama
Sign In
kit-mcp

kit-mcp

by luanpdd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

gates

List, fetch, or run reusable workflow gates for regression and confidence checks. Optionally auto-spawn a UI to stream progress.

Instructions

List, fetch, or execute reusable workflow gates (regression, confidence, etc).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "gates"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoFor action=get or action=run
stageNoFor action=for-stage
actionYes
autoSpawnNoOn action=run: auto-start the sidecar UI (kit ui) if not running and stream progress to it.
projectRootNoFor action=run

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.29.0
  2. Removedv1.22.0
  3. Addedv1.21.0
  4. Removedv1.15.0
  5. Changed4 schema fields changedv1.2.0
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "list",
-  "get",
-  "for-stage"
-]New value: +[
+  "list",
+  "get",
+  "for-stage",
+  "run"
+]
    • addedInput schema / properties / autoSpawn
      Added value: +{
+  "description": "On action=run: auto-start the sidecar UI (kit ui) if not running and stream progress to it.",
+  "type": "boolean"
+}
    • changedInput schema / properties / id / description
      Previous value: -"For action=get"New value: +"For action=get or action=run"
    • addedInput schema / properties / projectRoot
      Added value: +{
+  "description": "For action=run",
+  "type": "string"
+}
  6. First observedv0.4.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It minimally mentions actions like 'run' with autoSpawn sidecar, but lacks details on side effects, permissions, or state changes. The description is insufficient for a tool with 5 parameters and 2 enums.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence that conveys the core purpose. However, it could be structured with more detail on actions and parameters.

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?

Given the presence of 5 parameters and 2 enums, the description is too brief. It does not explain return values, combined parameter usage, or behavior for each action, leaving significant gaps for the AI agent.

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 80%, so the schema already documents most parameters. The description adds general context ('reusable workflow gates') but does not enhance understanding beyond the schema.

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?

The description clearly states the tool lists, fetches, or executes reusable workflow gates, with four explicit actions. However, it does not differentiate from sibling tools like 'kit' or 'sync', which could overlap in function.

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?

No guidance on when to use this tool versus alternatives. The description lists actions but does not specify scenarios for each action or when not to use the tool.

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