Skip to main content
Glama

Gate Init

gate_init

Initializes project health for a repo by building a graphify map, setting the dedup cache path, and providing an MCP slug hint; run once per repository.

Instructions

Project health: graphify map, dedup cache path, MCP slug hint. Run once per repo. See gate_help.

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": "gate_init"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectRootNoProject root (defaults to cwd / GATE_PROJECT_ROOT)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.12

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the artifacts created (map, cache path, slug hint) plus a re-run caution. It does not say whether existing artifacts are overwritten, where they are written, whether the operation is expensive, or what the response contains.

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

Conciseness3/5

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

It is short with no wasted sentences, and the cadence instruction is front-loaded. But the telegraphic noun-phrase fragments ('graphify map, dedup cache path, MCP slug hint') read as an unparsed keyword dump rather than a readable statement, hurting comprehension more than length does.

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?

No output schema and no annotations exist, yet the description never describes what the tool returns or where the produced artifacts live. For an initialization tool that mutates repo-local state, that is a meaningful gap for an agent deciding whether to call it.

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?

There is a single optional parameter with 100% schema description coverage, so the schema already explains projectRoot and its cwd/GATE_PROJECT_ROOT default. The description adds nothing about it, which is acceptable at this coverage level but leaves no extra value.

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

Purpose3/5

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

The description lists what the tool produces (a graphify map, a dedup cache path, an MCP slug hint) rather than stating a clear verb+resource action, so the reader must infer that it initializes project state. It is distinguishable from siblings like gate_graph_query or gate_compress_file, but terms like 'graphify map' are unexplained jargon.

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?

'Run once per repo' gives a concrete cadence and implicitly warns against repeated invocation. However, there is no statement of when NOT to use it, no prerequisites (e.g., must the repo be a git checkout?), and no alternatives beyond the pointer to gate_help.

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