Skip to main content
Glama
Sign In
guardvibe

guardvibe

by goklab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

scan_staged

Scans git-staged files for security vulnerabilities before you commit, catching issues early. Diff-aware by default, it reports only findings on newly-staged lines while skipping unchanged code.

Instructions

Scan git-staged files for security vulnerabilities before committing. Run this before every commit to catch issues early. No input needed — automatically reads staged files. Diff-aware by default: reports only issues on newly-staged lines (set diff_aware:false for whole staged files).

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

Input Schema

NameRequiredDescriptionDefault
formatNoOutput format: markdown (human) or json (machine-readable for agents)markdown
diff_awareNoReport only findings on newly-staged lines (true, default) vs. all lines in staged files (false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.66.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed1 schema field changedv3.21.0
    • addedInput schema / properties / diff_aware
      Added value: +{
+  "default": true,
+  "description": "Report only findings on newly-staged lines (true, default) vs. all lines in staged files (false)",
+  "type": "boolean"
+}
  3. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the behavioral burden. It discloses that no input is needed, that staged files are read automatically, and that diff awareness defaults to true, but it does not state whether the scan is read-only, what the output contains, or any repo/permission constraints.

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?

The description is short and front-loaded with the core action and timing. The only minor inefficiency is that 'before committing' and 'before every commit' restate the same timing point.

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?

Given the low-complexity schema and no output schema, the description gives enough for an agent to invoke it correctly. It could say more about the return shape or the format parameter, but the schema covers those details adequately.

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 baseline is 3. The description mentions diff_aware behavior, but this largely repeats the schema's own explanation and does not add syntax, defaults, or edge-case guidance beyond it.

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: scanning git-staged files for security vulnerabilities. The scope ('git-staged files', 'before committing') clearly separates it from sibling tools that scan directories, changed files, dependencies, or full projects.

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?

Explicitly says to run it before every commit, giving a clear usage occasion. It does not name alternatives or exclusion cases, such as when to prefer scan_changed_files or full_audit instead.

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

Deploy Server

Other Tools