Skip to main content
Glama

Guard Audit

codapult_guard_audit

Scan the entire repository against active Guard rules, including baseline-hidden findings, and validate policy contracts for a full architecture health review rather than changed-file checks.

Instructions

Scan the entire current repository against active Guard rules, including findings normally hidden by the baseline, and validate policy contracts. Use for a full health review; unlike codapult_guard_check, this is not limited to changed files. Returns findings, contract issues, counts, and overall status.

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

Input Schema

NameRequiredDescriptionDefault
rootNoProject path or workspace root.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/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 it does disclose that results include findings normally suppressed by the baseline, contract issues, counts, and an overall status. It does not mention cost, runtime, permissions, or that it is a read-only operation, which are gaps for a full-repository scan.

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, all load-bearing: the action and scope, the routing rule against the sibling, and the return contents. The contrasting alternative is front-loaded rather than buried.

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?

No output schema exists, and the description compensates by enumerating what comes back (findings, contract issues, counts, status). The lone optional parameter is fully documented in the schema. Only the absence of any note on runtime or permission expectations keeps it from a 5.

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 coverage is 100% and the single optional 'root' parameter is documented in the schema as project path or workspace root. The description adds nothing beyond that, so the baseline 3 applies.

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: 'Scan the entire current repository against active Guard rules', plus a secondary capability of validating policy contracts. It explicitly contrasts with codapult_guard_check, so an agent can distinguish it from that sibling 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?

Names the intended scenario ('full health review') and the alternative ('unlike codapult_guard_check, this is not limited to changed files'), which is the exact discriminator an agent needs to choose between them. Both the when and the when-not are present.

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