Skip to main content
Glama

Decide Guard Proposals

codapult_guard_proposal_decide

Approve or reject current architecture proposals: approval activates selected Guard policy rules and contracts, while rejection records the decision without activation.

Instructions

Record an explicit approval or rejection for the selected current proposals. Approval activates the selected rules/contracts in Guard policy; rejection records the decision without activation. Stale proposals cannot be decided, and protected approval policy may require a non-MCP reviewer. Returns the decision and affected IDs.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ids": "<ids>",
      "decision": "<decision>"
    },
    "name": "codapult_guard_proposal_decide"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesOne or more proposal IDs from the current codapult_guard_propose result.
rootNoProject path or workspace root.
confirmNoMust be true before recording decisions or activating proposals.
decisionYesWhether to activate the selected proposal(s) or record their rejection.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.13.2
    • changedInput schema / properties / confirm / description
      Previous value: -"Required before changing Guard state."New value: +"Must be true before recording decisions or activating proposals."
    • addedInput schema / properties / decision / description
      Added value: +"Whether to activate the selected proposal(s) or record their rejection."
    • addedInput schema / properties / ids / description
      Added value: +"One or more proposal IDs from the current codapult_guard_propose result."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well: it discloses that approval activates rules/contracts, rejection records without activation, stale proposals are rejected, and protected approvals may need a non-MCP reviewer. It still omits details like the confirm=true requirement and whether an approval can be undone.

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?

Four short sentences, front-loaded with the action and effects, then constraints, then return. No repetition or filler; every sentence adds useful information.

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 mutation/decision tool with no annotations and no output schema, the description supplies purpose, side effects, constraints, and return shape. It is largely complete, though it could state the confirmation requirement and reversibility more explicitly.

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 the schema already documents ids, root, confirm, and decision. The description adds little parameter-level meaning beyond 'selected current proposals' and return IDs, so baseline 3 is appropriate.

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?

States a specific verb (record) and resource (selected current proposals) and clearly distinguishes approval from rejection. It is clear, but it does not explicitly name or differentiate from sibling tools such as codapult_guard_propose, so it falls short of the top score.

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?

Gives clear usage context: decisions apply to selected current proposals; approval activates rules/contracts while rejection records without activation. It also states two constraints (stale proposals cannot be decided, protected approvals may require a non-MCP reviewer), though it does not route the agent to sibling tools such as review or verify.

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