Skip to main content
Glama
Sign In
kit-mcp

kit-mcp

by luanpdd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

ack-restart

Removes the restart-required marker after an IDE restart, stopping kit:doctor warnings. Called automatically or manually to acknowledge the restart.

Instructions

Acknowledge that the IDE session was restarted after kit:auto-install. Removes the .kit-mcp-restart-required marker so kit:doctor stops warning. Called automatically by the harness when it detects the marker after reload, or manually by the user.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ack-restart"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectRootNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.29.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden. It states it removes a marker and stops a warning, disclosing a write operation. No additional behavioral details beyond what is implied.

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?

Three concise sentences front-load the purpose and add usage context. No wasted words.

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 simple tool with one parameter and no output schema, the description covers purpose and usage but lacks parameter explanation, which is a gap.

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?

There is one parameter (projectRoot) with no description in the schema (0% coverage). The description does not explain its meaning or usage, leaving the agent uninformed.

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 tool's purpose: acknowledge IDE restart after kit:auto-install by removing a marker. It distinguishes from sibling tools like auto-install and kit by focusing on the acknowledgment step.

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

Usage Guidelines4/5

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

The description explains when to use the tool: automatically by the harness after reload or manually. It does not explicitly exclude other contexts but the intent is clear.

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