Skip to main content
Glama

Guard Check

codapult_guard_check

Run active architecture rules and contract validation to return structured findings and pass/fail status. Focus on changed files with baseline respect, or scan the full project for a fast deterministic policy check.

Instructions

Run active architecture rules and contract validation, returning structured findings and status. Use for a fast deterministic policy check: changed_only=true focuses on changed files and respects the baseline; false scans the full project. Omitted uses the scanner default. For a full audit that ignores baseline suppression, use codapult_guard_audit.

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

Input Schema

NameRequiredDescriptionDefault
rootNoProject path or workspace root.
changed_onlyNoLimit rule findings to changed files; true respects the baseline, false scans the full project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.13.2
    • addedInput schema / properties / changed_only / description
      Added value: +"Limit rule findings to changed files; true respects the baseline, false scans the full project."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden, and it does disclose meaningful traits: deterministic execution, that changed_only=true respects the baseline, that an omitted value falls back to the scanner default, and that audit differs by ignoring baseline suppression. It does not describe side effects or what 'status' represents, which keeps it short of a 5.

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 earning its place: what it does, how to use it with parameter branching, and where to go instead. The key routing information is front-loaded before the alternative.

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 two-optional-parameter check tool this is close to sufficient, but with no annotations and no output schema, 'structured findings and status' leaves the agent guessing about return shape (e.g., what status values mean, whether findings include severity or file locations). Some additional return-value context would close the gap.

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 100%, so both parameters are already documented. The description adds only the omitted-value default ('uses the scanner default'), which is a small increment over the schema's existing explanation of the true/false semantics; this is the baseline 3 case.

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 opens with a specific verb+resource phrase: 'Run active architecture rules and contract validation,' and states that it returns findings and status. It also names the sibling it is not (the full audit), so an agent can distinguish it from codapult_guard_audit without opening either schema.

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

Usage Guidelines5/5

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

It states the use case ('a fast deterministic policy check'), explains the changed_only branching, and explicitly routes the agent to codapult_guard_audit when baseline suppression must be ignored. When-to-use, when-not-to-use, and the alternative are all present.

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