Skip to main content
Glama

krusch_context_nudge

Read-onlyIdempotent

Audits staged code or unified diffs against active project invariants, returning up to three findings to catch issues before commit.

Instructions

Audit staged code or unified diffs against active project invariants (max 3 findings).

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": "krusch_context_nudge"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeNoCode or unified diff to audit
triggerNopre_commit
file_pathNoOptional target file path for git blame attribution
enable_lego_guardNoOptional flag to force INV-LEGO-01 boilerplate check

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds one genuine behavioral fact beyond them: results are capped at three findings, which tells the agent output is truncated. It does not explain what 'active project invariants' are, where they come from, or what happens when more than three findings exist.

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?

A single front-loaded sentence with no filler; the finding cap is appended compactly where it matters. Nothing would be gained by trimming.

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 read-only, no-required-params tool with no output schema, the description is adequate but leaves the agent guessing on two things: what counts as an 'active project invariant' and what the undocumented 'trigger' parameter accepts. The finding cap partially compensates for the missing output schema.

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 75%, so three of four parameters are already documented and the baseline of 3 applies. The description adds no parameter-level meaning beyond the schema — notably the 'trigger' parameter has neither a description nor an enum, and the description does not clarify its accepted values or what 'pre_commit' changes.

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 ('audit') and resource ('staged code or unified diffs') with a clear scope ('active project invariants'), which separates it from siblings like krusch_diff or krusch_explain. It does not explicitly name a sibling or contrast behavior, so it stops short of full differentiation.

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?

The phrase 'staged code or unified diffs' and the default trigger of pre_commit imply a pre-commit review workflow, but the description never states when to prefer this over krusch_diff or krusch_explain, nor any exclusions. Usage must be inferred.

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