Skip to main content
Glama
guardvibe

guardvibe

by goklab

check_project

Scan multiple files for security vulnerabilities and generate a project-wide security report with a security score for comprehensive audits.

Instructions

Scan multiple files for security vulnerabilities and generate a project-wide security report with a security score. Use this for comprehensive security audits.

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": {
      "files": "<files>"
    },
    "name": "check_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesYesList of files to scan: [{path, content}]
formatNoOutput format: markdown (human) or json (machine-readable for agents)markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.66.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / files / items / additionalProperties
      Removed value: -false
  2. Addedv3.35.1
  3. Removedv3.30.0
  4. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the outcome (a project-wide report plus a numeric security score) and implies a non-mutating analysis, but says nothing about file-count or size limits, whether it needs network access, or how large projects are handled.

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?

Two tight sentences with the capability and output stated up front and no filler. Every sentence earns its place.

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 two-parameter read-style tool whose schema is fully documented and whose deliverable is named, this is largely complete. The remaining gap is routing against the many overlapping scan/audit siblings, not the call mechanics.

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 both parameters — the files array with path/content and the markdown/json format enum — are fully documented in the schema. The description adds no meaning beyond that, which makes the baseline 3 correct.

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 and scope: scan multiple files across a project and produce a report with a security score. That is clear, but it never distinguishes itself from siblings like full_audit, deep_scan, or check_code, which read as overlapping capabilities.

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?

"Use this for comprehensive security audits" hints at the appropriate context, but with 35 sibling tools including full_audit and deep_scan, the description never says which to pick or when this one is wrong. Usage is implied rather than routed.

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