Skip to main content
Glama

Guard Next Action

codapult_guard_next_action

Determines the next bounded Guard workflow step by checking setup, stale facts, changed-file findings, and policy contracts, returning an action and reason without writing files.

Instructions

Choose the next bounded step in the Guard workflow without writing project files. Call at task start or after a step: it checks setup, stale project facts/proposals, changed-file findings, and policy contracts, then returns an action such as init, analyze, policy review, repair, or verify with the reason.

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_next_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
rootNoProject path or workspace root.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the load and does well: it discloses that no project files are written, and enumerates the inputs it evaluates (setup, stale facts/proposals, changed-file findings, policy contracts) plus the action+reason return. It stops short of stating whether any state is mutated or cached.

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?

Two dense sentences, front-loaded with the purpose and the read-only guarantee before the diagnostic detail. 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 router-style tool with one trivial param, the description covers what is checked and the shape of the return value even without an output schema. The minor gap is how the returned action maps to invoking the corresponding sibling tool.

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?

The single parameter 'root' already has a full schema description ('Project path or workspace root') at 100% coverage, so the baseline is 3. The description never mentions root or defaults, adding nothing beyond the schema.

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?

States a specific verb and resource ('Choose the next bounded step in the Guard workflow') and enumerates the decision outputs (init, analyze, policy review, repair, verify), which cleanly separates it from the sibling tools that perform those actions.

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?

'Call at task start or after a step' gives explicit timing for invocation and implicitly routes the agent to the sibling it names as the resulting action. It lacks an explicit 'do not use this when…' exclusion, so it falls just short of a 5.

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