Skip to main content
Glama

Guard Context

codapult_guard_context

Reads the project model, architecture insights, conventions, policy, proposals, baseline, waivers, and completion-gate settings in one response; refresh selects current or persisted context.

Instructions

Read the project model, architecture insights, conventions, active policy, proposals, baseline, waivers, and completion-gate settings in one structured response. Works before Guard initialization. Use refresh=true (default) for current repository state; refresh=false prefers persisted snapshots and is useful when inspecting the last saved model.

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

Input Schema

NameRequiredDescriptionDefault
rootNoProject path or workspace root.
refreshNoRediscover the working tree and derive current context; false prefers persisted model and memory artifacts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.13.2
    • changedInput schema / properties / refresh / description
      Previous value: -"Rediscover the working tree instead of reading the persisted snapshot."New value: +"Rediscover the working tree and derive current context; false prefers persisted model and memory artifacts."
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden, and it does cover the read/observe nature and the pre-initialization case. It is silent on side effects — notably whether refresh=true rediscovers and *persists* a model or is purely non-mutating — and says nothing about cost or latency of 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.

Conciseness4/5

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

Three tight sentences, front-loaded with what is returned, then the pre-init caveat, then the refresh tradeoff. The long enumeration is dense but each item is informative; 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?

No output schema exists, so the description correctly compensates by enumerating the returned sections, and it flags the pre-init usability constraint. The remaining gap is side-effect/persistence disclosure for refresh=true, which matters for a tool that may write artifacts.

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%, so both parameters are already documented; the description's refresh guidance largely restates the schema's own wording. The 'root' parameter gets no added meaning at all, so the baseline 3 holds.

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?

Uses a specific verb ('Read') plus an enumerated set of resources (project model, architecture insights, conventions, active policy, proposals, baseline, waivers, completion-gate settings), so the agent knows exactly what comes back. It does not name any sibling, so the boundary with codapult_guard_governance or codapult_guard_audit must be inferred.

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?

Gives a real usage condition ('Works before Guard initialization') and explains when to pick each refresh mode, which is more than most. But it never states when not to use this tool or which sibling to prefer for a narrower question, leaving sibling selection to inference.

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