Skip to main content
Glama

Guard Governance Audit

codapult_guard_governance

Audit governance trails by checking proposal and approval provenance, policy bindings, and evidence reachability from decisions; reports declared metadata, not identity or signature verification.

Instructions

Inspect proposal and approval provenance metadata, policy bindings, and whether retained verification evidence is reachable from decisions. Use for a governance trail audit; output describes declared metadata and does not authenticate identities or verify signatures.

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

Input Schema

NameRequiredDescriptionDefault
rootNoProject path or workspace root.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 behavioral burden. It usefully discloses a key limitation — output describes declared metadata and does not authenticate identities or verify signatures — but does not otherwise state permissions, read-only nature, or output shape.

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

Conciseness4/5

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

Two compact sentences, front-loaded with the inspection scope and followed by the usage and limitation. No wasted language, though the second sentence packs multiple caveats without much structure.

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?

The description covers purpose and a major limitation, but with no output schema and no annotations it does not fully describe what output to expect beyond 'declared metadata'. A governance audit tool with many siblings could benefit from more explicit routing guidance.

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 only parameter (`root`) is fully described in the schema with 100% coverage, so the schema does the heavy lifting. The description adds no additional meaning about the path format or scope beyond what the schema already provides.

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?

The description states a specific verb (Inspect) and a well-defined resource scope: proposal/approval provenance metadata, policy bindings, and evidence reachability. It is clear what the tool examines, though the sibling `codapult_guard_audit` creates potential overlap that the description does not explicitly resolve.

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?

It gives one positive usage cue ('Use for a governance trail audit') but does not say when to choose this over the many nearby siblings such as `codapult_guard_audit`, `codapult_guard_review`, or `codapult_guard_verify`. No exclusions or alternatives are named.

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