Skip to main content
Glama

Initialize Guard

codapult_guard_init

Initialize Guard policy, project model, and supporting artifacts for repositories without existing Guard state; preserves current state by default and reports setup findings.

Instructions

Create the initial Guard policy, project model, and supporting artifacts for a repository that has not been initialized. Existing Guard state is preserved by default. Use force only to replace existing state after reviewing the consequences; the result reports initialization findings.

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

Input Schema

NameRequiredDescriptionDefault
rootNoProject path or workspace root.
forceNoReplace existing Guard artifacts, including the baseline; requires confirm=true.
confirmNoRequired before writing Guard artifacts.
no_waitNoReturn immediately if another process holds the Guard state lock.
wait_msNoMaximum time to wait for the Guard state lock, in milliseconds.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.13.2
    • changedInput schema / properties / force / description
      Previous value: -"Replace existing Guard state; requires confirm."New value: +"Replace existing Guard artifacts, including the baseline; requires confirm=true."
    • addedInput schema / properties / no_wait / description
      Added value: +"Return immediately if another process holds the Guard state lock."
    • addedInput schema / properties / wait_ms / description
      Added value: +"Maximum time to wait for the Guard state lock, in milliseconds."
  2. First observed

TDQS

A4.1/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 and does reasonably well: it discloses default non-destructiveness ('Existing Guard state is preserved by default') and what force destroys ('replace existing state'). It omits the lock/wait behavior and the confirm gate, but those are documented in the schema.

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 sentences, each doing distinct work: what is created, the safe default, and the force caveat plus result. Front-loaded with the purpose and no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 5-param, zero-required, no-output-schema initialization tool, the description covers purpose, default safety, and the destructive override. It could have mentioned the confirm requirement or lock waiting, but the fully documented schema fills those in.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3; the description adds genuine value by explaining the intent behind 'force' (only after reviewing consequences) and the default-preservation behavior, which contextualizes the boolean rather than just restating it.

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?

Uses a specific verb ('Create') with concrete artifacts ('initial Guard policy, project model, and supporting artifacts') scoped to 'a repository that has not been initialized'. An agent can distinguish this as the bootstrap step versus the analyze/verify/propose siblings, though no sibling is named explicitly.

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?

States the precondition ('a repository that has not been initialized') and gives explicit guidance on the risky path: 'Use force only to replace existing state after reviewing the consequences'. It does not name alternative tools (e.g., next_action, check) or say what to do when state already exists, so it falls short of full when/when-not routing.

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